Re: Fix LXC container creation for Wheezy point release
On Wed, 2013-05-08 at 13:05 +0200, Sjors Gielen wrote:
> There's a better solution: Rob has a fixed template that does not use
> live-debconfig, and he said he is willing to support it. The release
> team suggested the solution that a non-maintainer upload is done with
> the working template in it. Once this is done, a bug can be opened with
> release.d.o that explains the situation; if this happens in time, the
> fix may be in the first Wheezy point release. That would make the lxc
> package significantly more useful. (live-debconfig is already in
> Jessie, so this is not relevant there.)
>
> Rob, are you willing to pick this up? It would come down to replacing
> the templates in debian/local, then upping the version to something
> like 0.8.0~rc1-8+deb7u1-wheezy1. Once you've got a new source package,
> we can open a release.d.o bug. I'm not a Debian maintainer myself, and
> my own experience here is limited to creating packages that are used
> internally and never uploaded to the archive, but if needed I'll help
> you if I can.
>
Hi Sjors, Daniel and release-folks,
I am still willing to support my alternative Debian container template.
I have been using this template for two years now on different processor
architectures (armel/i386/amd64) and it seems to be bug-free. If bugs
are reported I will try to fix them, but I will not add extra functions
to the template.
Unfortunately I know very little about packaging and how the release
process works. I hope to learn about these things some time in the
future. At the moment I am busy with a project to enhance Linux security
a little bit (using the technology behind LXC: kernel namespaces and
cgroups). It's early days and the project needs my full attention so I
don't want to spend time on packaging.
A LXC template is just a script to create a rootfs. It's no problem to
have multiple Debian templates in the package, so maybe the solution is
simple: just add my template to the package?
Kind regards,
Rob.
http://freedomboxblog.nl
Reply to: