[Pkg-cryptsetup-devel] updated cryptsetup package for ubuntu

[Reinhard Tartler]

Hi Martin & Alasdair,

I'm mailing you because you have registered yourself as bug contact for
the cryptsetup package in ubuntu according to the portlet on
https://launchpad.net/ubuntu/+source/cryptsetup. I therefore assume you
somehow intend to "maintain" the package in ubuntu. 

I'm CC'ing the cryptsetup devel mailing list to you, the cryptsetup
maintainers that we do care about cryptsetup in ubuntu & debian, and how
we intend to maintain it in ubuntu. I'm also CC'ing the ubuntu-motu
mailing list, because I know that at least SOME other motus have looked
at the package in the past as well ;) - feel free to add yourself as
further bug contacts.

I've played around a bit with bzr-builddeb and bzr-svn, and have
imported the debian cryptsetup svn to the bazaar supermirror, so that we
can access the old svn history via bzr!

To update the 'debian.trunk' bzr branch, which can be found e.g. at
https://code.launchpad.net/~siretart/+branch/cryptsetup/debian.trunk,
From the svn sources with installing the bzr-svn package from feisty,
and the following command:

bzr pull --remember svn://svn.debian.org/pkg-cryptsetup/cryptsetup/trunk

Ideally, this should be done by the vcs import system in launchpad, but
as I said, I wanted to play a bit with bzr-svn.

You'll notice that only the 'debian' directory is versioned. The reason
is that the debian cryptsetup team prefers to use the svn-buildpackage
'mergeOnUpstream' mode. Such branches can be build in bzr using
bzr-builddeb, also available for bzr 0.14 in feisty. By default, it
looks for orig.tar.gz's in ../tarbals, but this can be overridden by a
config file:

>> cat ~/.bazaar/builddeb.conf
[BUILDDEB]
orig-dir = /srv/scratch/tarballs

To actually build the package, use 'bzr bd'. See 'bzr help bd' for
various further options like specifying your own builder or just
exporting the package. I've also setup a wiki page explaining more about
bzr-builddeb: https://wiki.ubuntu.com/BzrBuildpackage

Okay, now for the status update for cryptsetup in feisty: I've prepared
a new merged package here (download it with `bzr get <url>`):

https://code.launchpad.net/~siretart/+branch/cryptsetup/ubuntu

I'm currently not at home yet, so I didn't have the change to test it
properly, but there are no merge conflicts left, and I think we really
should get to to feisty before the UVF (upstream version freeze) on
Wednesday. It would be great if some more people could eyeball it and
look if it can be uploaded to feisty.

On https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bugs, there are
a lot of bugs with patches, which need to be reviewed and integrated
into the cryptsetup package. Many of them aren't that well thought, and
need serious eyeballing, but this can safely be done after the UVF. The
important patches in addition to the debian package is the usplash
termination patch, and the console redirection for upstart.

I think both patches are interesting for debian as well. They can be
found e.g. here:
http://patches.ubuntu.com/c/cryptsetup/cryptsetup_2:1.0.4-8ubuntu2.patch. I
didn't forward them to debian yet, because I wanted to evaluate if the
usplash patch applies to the debian splashy package as well, but I
haven't found the time for it yet, sorry. The upstart patch, well,
upstart can be found in debian/experimental as well, so I'm pretty sure
it's necessary with that as well.

Thank you for your attention so far, I hope you find this post
interesting. Feel free to give me feedback about cryptsetup maintenance
in ubuntu and debian, your plans with it, and also any problems you
encounter with bzr-builddeb!

-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 213 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-cryptsetup-devel/attachments/20070204/7653f98c/attachment.pgp