On 04.05.13 20:47, Holger Levsen wrote:
Same here. I think the confusion arised over whether installing cloud-init from wheezy backports (which I support) or whether installing cloud-init from wheezy-backports and adding wheezy-backports to the sources.lists of those images (which I don't support, as it's not done for default debian installations either).
I think that could be an acceptable compromise, but the image would then include a package without its corresponding source. I'm playing devil's advocate here, but isn't that against some debian policy ?
Since the package's only purpose is to initialize the image, security updates don't seems like much of a concern, but at the very least it feels a bit weird.
Christian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
