Bug#756986: wheezy-pu: package debian-lan-config/0.13~bpo70+5
Control: tags -1 + moreinfo
On 2014-08-04 9:19, Andreas B. Mundt wrote:
I would like to ask for the permission to upload and the inclusion of
the latest debian-lan-config package in the upcoming wheezy point
release.
The debian-lan-config package is kind of special, as it contains no
'program' in itself, but instructions (in a FAI config space) on how
to build a composed system within debian, cf.
<URL:https://wiki.debian.org/DebianLAN>.
The package did not make it for the wheezy freeze and I provided it
Many packages didn't make the freeze. That doesn't mean we should add
them all to stable.
Looking at the package's upload history, the first upload reached the
archive a few weeks before the wheezy release, with the first upload to
unstable being on the day of the release. That's really not the same as
"did not make it for the wheezy freeze", which had happened almost a
year earlier.
via backports after the release. However, with further improvements,
it got less and less justified to use backports, as the wheezy package
is not a strict 'backport' of the version in jessie, which is of
course targeted at jessie.
Given it's a configuration package, the diffstat of
66 files changed, 390 insertions(+), 245 deletions(-)
doesn't look crazy for a backport. Reading the unstable changelog, I
have to admit that I'm not sure why you're maintaining the backport as a
separate branch and wonder how big the diff would be if one took the
current package from testing and then applied the changes required for
wheezy.
Content and history of the package is available here:
<URL:http://anonscm.debian.org/cgit/collab-maint/debian-lan.git/log/?h=wheezy>
The package should not pose any risk to the distribution, as it needs
to be 'activated' manually to do anything at all. To get an idea, cf.
It's not a question of "posing a risk", but rather what compelling
reason there is to break the general policy of adding new packages to
stable - particularly a package that was barely in the archive when
stable released.
Regards,
Adam
Reply to: