Hi, appearantly some maintainers don't want to support backports in wheezy-backports anymore, saying wheezy is oldstable now (und unsupported by Debian proper, "just" maintained by the Debian LTS team.) In a way, that's a fair stand, as when they agreed to support the backport for the life time of wheezy, it probably wasn't clear that this means "until 2018" and not until 2016. (Wheezy-LTS was rather recently implemented.) OTOH, having unsupported backports with known security vulnerabilities is bad. So an option would be to _close_ wheezy-backports _now_, also to communicate this issue to the users. Removing individual backports from wheezy-bpo is both error prone and manual busy work on the shoulders of the bpo admins, who wouldn't want to do this job. Alternativly, the backports maintainers would need to agree to maintain those backports for two more years. What do you think? -- cheers, Holger (There is also the problem that some maintainers don't support their backports during the life time of stable, but that's a different problem IMO. Now we have the problem that backports need to be supported for up to 5 years instead of 3 too… this mail is about this 5y problem.)
Attachment:
signature.asc
Description: Digital signature