Re: Accepted debian-lan-config 0.13~bpo70+5 (source all)
Hi Alexander,
On Mon, May 12, 2014 at 09:32:49AM +0200, Alexander Wirt wrote:
> On Mon, 12 May 2014, Andreas B. Mundt wrote:
> > On Sun, May 11, 2014 at 10:31:04PM +0200, Alexander Wirt wrote:
> > > On Sun, 11 May 2014, Andreas B. Mundt wrote:
[...]
> > > > 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.
> I think you misunderstood how backports work. You also don't followed the
> recent discussions on the (mandatory) users list.
>
> - The source of of (stable-)backports is testing.
> - Do as less changes as possible
> - Don't differ from the version in testing unless you really have to.
This is all clear to me and I understand the reasons behind it.
However, debian-lan-config is a package which especially targets a
Debian release. It includes instructions how to build a composed
system from a Debian release. This depends of course on the release.
The version in stable-backports targets wheezy (the package could not
be finished before freeze, also because a rather 'stable' system is
needed to prepare/finish the package). The version in testing is
going to target jessie.
Using the testing version for stable-backports does not make any sense
(apart from fulfilling rules). Most of the differences between the
versions in testing and stable are related to the particular release.
So fulfilling the rules to the letter for the debian-lan-config
package leads to the following contradiction:
→ Either, the version in testing is still targeted onto stable
(and 'broken by design' for testing), or
→ the changes are by no means minimal.
I tried to solve this problem by preparing a wheezy branch in git [1]
and cherry-picking the minimal modifications relevant for the stable
version which is upload to stable-backports. This way, I hoped to
keep things clear, transparent and in the spirit of the rules. I am a
bit unhappy that you allege me not caring at all about those rules and
not reading mandatory lists. But I have not found any other sensible
way for a rather special package like debian-lan-config. If you can
suggest a better work flow, I am happy to adopt it.
Best regards,
Andi
[1] http://anonscm.debian.org/gitweb/?p=collab-maint/debian-lan.git
Reply to: