[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Accepted debian-lan-config 0.13~bpo70+5 (source all)



Hi Alexander,

On Sun, May 11, 2014 at 10:31:04PM +0200, Alexander Wirt wrote:
> On Sun, 11 May 2014, Andreas B. Mundt wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> >
> > Format: 1.8
> > Date: Sun, 11 May 2014 21:16:09 +0200
> > Source: debian-lan-config
> > Binary: debian-lan-config
> > Architecture: source all
> > Version: 0.13~bpo70+5
> > Distribution: wheezy-backports
> > Urgency: medium
> > Maintainer: Debian LAN Developers <debian-lan-devel@lists.alioth.debian.org>
> > Changed-By: Andreas B. Mundt <andi@debian.org>
> > Description:
> >  debian-lan-config - FAI config space for the Debian-LAN system
> > Changes:
> >  debian-lan-config (0.13~bpo70+5) wheezy-backports; urgency=medium
> >  .
> >    * Improved automatic kerberos machine key distribution.
> >    * Installation:
> >      - Add check if the network (APT repository) is available.
> >      - Add hook to remove old partition table before installation.
> >    * Icinga improvements:
> >      - no email notifications for client machines
> >      - monitor upgradable packages on diskless machines
> Eh hu? This is a +5 and this changelog? Please explain.


I backport the improvements from master to the wheezy version from
time to time.  Currently, I am working on debian-lan for jessie
(0.14), but no upload to jessie has been prepared, because a lot of
stuff regarding jessie is still in flux.

Alternatively, I could release non-ready packages to jessie (0.14,
0.15, ...) which do not fully work there and backport those packages
(i.e. their relevant parts) back to wheezy.  (The Version in wheezy
must not exceed the version in jessie).

If this strategy is causing problems, extra work or is in any other
way problematic, I am happy to learn a better one.

Best regards,

     Andi


Reply to: