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

Re: Bug#747697: [LCFC] templates://debian-security-support/{debian-security-support.templates}



Christian PERRIER wrote...


debian/control:
> Source: debian-security-support
(...)
> Description: Debian security support coverage checker
>  For some Debian packages, it is not feasible to maintain full security
>  support for all use cases through the full distribution release
>  cycle.
>  .
>  This package provides a program to identify installed packages for
>  which support has had to be limited or prematurely ended, and to
>  alert the administrator.

This wording is somewhat hard to read but I'll leave that to the
native English speakers.

>  New versions of this package with updated checklists are provided
>  via security updates.

... and that's not the full truth. Security updates will indeed
provide new version for stable (not implemented yet but I expect this
to happen soon) and oldstable (but not for squeeze since squeeze is
almost EOL). For squeeze-lts, new versions will be provided by
squeeze-lts, and while that one looks a lot like an extended
oldstable-security, it isn't from a technical point of view. Finally,
new versions for testing have little sense, for unstable none at all,
debian-security-support exists there for technical reasons only and
perhaps should be removed there once we've established the full
distribution path.

So, this package is rather unusual and I hope I'll finally find the
time to propose a policy extension that will allow us to drop it in
jessie+2.

About the wording, it should be kept generic since the squeeze-lts
name will vanish, and perhaps the entire LTS project (I hope not). So
I'd just suggest something short like:

>  Updated checklists are provided via regular and/or security updates.

or:

>  Updated checklists are provided by new package versions.

[ intermission, there's more to come on other parts that need l10n  ]

    Christoph

Attachment: signature.asc
Description: Digital signature


Reply to: