Re: cloud-init is marked for autoremoval from testing

Hi, this is a friendly reminder that the cloud-init package is being removed in less than 1 week from now. The fix for pep8 problem (+ others) is still available from <https://gitlab.com/puttus/cloud-init.git>. Joonas Kylmälä: > Hi, > > Debian testing autoremoval watch: >&g

Re: cloud-init is marked for autoremoval from testing

repositories from debian defaults. All the changes have been tested by me and confirmed working at least on my setup. Best regards, Joonas Kylmälä

Re: cloud-init is marked for autoremoval from testing

Emmanuel Kasper: > The initial bug report is from 22 Juni, so you need to let the > maintainer some time to react it. I understand – being just a bit too excited when I learned how easy it is to contribute to Debian (you only need text editor and email)! :) > Thanks for the PEP-8 patch, I had a

Bug#866613: cloud-init: Adding Apache v2 license to debian/copyright

Package: cloud-init Version: 0.7.9-2 Severity: wishlist Dear Maintainer, Since the version 0.7.9 of cloud-init it has been available also with the Apache License version 2.0. Refer to the release notes available on . Could we make the Debian package

Bug#834612: cloud-init: [INTL:nl] Dutch translation of debconf messages

Frans Spiesschaert: > I did so (see > https://lists.debian.org/debian-l10n-dutch/2017/06/msg00166.html and > follow up). > I attach a slightly modified translation. Awesome! I added it to my repository at . Hopefully it will soon hit the offical one, too

Bug#866613: cloud-init: Adding Apache v2 license to debian/copyright

We need to also take care of asking permission from the authors of Debian patches if they can be used under Apache v2 license.

Re: cloud-init is marked for autoremoval from testing

Joonas Kylmälä: > Thank you Emmanuel for the review! The mock-meta.py code doesn't get > included in the Debian binary package at all so in my opinion we can > just leave it like that for now. However, as you raised this topic up, I > will submit now a patch to the upstream to fi

Bug#846526: cloud-init: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

Hey Adriano, On Sat, 3 Dec 2016 22:48:59 -0200 Adriano Rafael Gomes wrote: > After researching about the fallback data source, I would propose a new > round of translations. > http://cloudinit.readthedocs.io/en/latest/topics/datasources/fallback.html > > Marcin, can you

Bug#865611: marked as done (non-free repositories are enabled by default)

There was no conclusion about whether this change will be added to the stable/oldstable version. Can you Thomas say anything about this? Joonas

Bug#865611: non-free repositories are enabled by default

Joonas Kylmälä: > I'm pretty confident with the modifications to > "sources.list.debian.tmpl" but for "sources.list.ubuntu.tmpl" I would > like to get your opinions on how to edit it. The official Ubuntu > 17.04 with default installation appears to be enabled w

Bug#735207: cloud-config will never start on upstart

I think this bug can be closed now as upstart has been removed from Debian (see #808289)?

Bug#845019: Instructions for backports are out-of-date

New stable (stretch) was just released so the issue is not anymore in stable. Should we just close this bug?

Bug#865577: cloud-init FTBFS: recipe for target 'pep8' failed

This bug has been fixed in the upstream commit .

Bug#865611: non-free repositories are enabled by default

think we should give a higher priority to this bug as it affects the Debian OpenStack images as discussed on this thread: <http://lists.alioth.debian.org/pipermail/openstack-devel/2017-June/021344.html>. Best regards, Joonas Kylmälä

Bug#846526: cloud-init: [INTL:pt_BR] Brazilian Portuguese debconf templates translation

Adriano Rafael Gomes: > Hi. Please accept the attached file. Has it been reviewed?

Vagrant Boxes

Hi, In Vagrant Cloud I see mostly Virtualbox Vagrant Boxes. Can I somehow help with getting some free providers working with the image, like libvirt, lxc or docker? Is the problem that there is no packer setup for the other Vagrant providers? So if I would create those packer setups and send a

Re: Vagrant Boxes

Hi, Emmanuel Kasper: > I see also that you expressed interess to create Vagrant Boxes for > Docker. We haven't start anything there but I would be interesting to > hear if such a thing is possible with fai[1] the tool we evaluate to use > in the future for all boxes. > If you want to play around

Re: Vagrant Boxes

Antonio Terceiro: > https://app.vagrantup.com/debian/boxes/stretch64 > > ^ libvirt and lxc are already available. what exactly are you missing? Latest version of Jessie (and Testing) is missing them. I see there has been lxc and libvirt previously so I thought maybe something happened (like some

Re: Re: Problem creating Vagrant boxes

Hi, I couldn't reproduce the DNS resolution problem anymore. They both use the same deb.debian.org package repository so when I noticed this problem about ~1 month ago I ran "sudo apt update" on the 9.2.0 image it wasn't able to fetch the packages but with 9.1.0 it was. I have no idea what made

Re: Problem creating Vagrant boxes

I had also the DNS resolution problem with the latest Debian Stretch VirtualBox image, 9.2, which was downloaded from the Vagrant Cloud. Emmanuel Kasper: > Le 17/11/2017 à 12:53, Christopher Huhn a écrit : >> Dear Debian Cloud Team, >> >> on the occasion of re-investigating vagrant I stumpled