Re: dhcpcd is gone on Jessie, which DHCP client is recommended for Jessie Debian AMIs?

❦ 5 août 2014 22:56 +0200, Tomasz Rybak tomasz.ry...@post.pl : I'm testing bootstrap-vz and it would like to install dhcpcd but it is not present on Jessie. isc-dhcp-client and isc-dhcp-common are intentionally excluded during bootstrapping and our wiki also recommends avoiding them:

Re: bootstrap-vz switching to single branch strategy

❦ 3 mai 2015 04:43 +0200, Eirik Schwenke debian-li...@s.hypertekst.net : I was wondering; are there any plans to make it more usable as a regular user? It seems it shouldn't be necessary to run it as root (at least not in all use-cases)? Have a look at unshare which allows to become root

Re: Debian images on Microsoft Azure cloud

❦ 12 novembre 2015 16:34 +0100, Thomas Goirand  : >>> I just created wiki page[1] where we could put those requirements. It's >>> simple but should do the job. >>> >>> 1. https://wiki.debian.org/Cloud/Images_requirements >> >> Currently, both the Openstack images and the image

Re: Debian images on Microsoft Azure cloud

❦ 11 novembre 2015 17:49 GMT, Marcin Kulisz  : >> I would suggest we open a seperate thread on the debian-cloud mailing >> list for defining a list of official requirements for all vendors. As >> long as we define the first version of that list i would suggest though >> that

Re: Cloud images with backports APT-enabled.

❦ 30 novembre 2015 22:31 +0900, Charles Plessy  : >> > In the case of cloud images, wouldn't that problem be solved by pinning the >> > backports suite at a low priority, and pinning the installed backports >> > (cloud-init, etc.) at a higher priority ? > > Le Sat, Nov 28,

Re: About non-Stable files in Cloud images: create a Blend ? Distribute image builders on ftp.debian.org ? More liberal Stable updates ? (Re: Debian images on Microsoft Azure cloud)

❦ 26 novembre 2015 08:25 -0500, Brian Gupta  : >> On the Stable release, we have updates for the Kernel to add new >> drivers, previously not supported. I really consider that the support of >> new clouds (for example through an update of cloud-init) is exactly the >>

Re: Debian images on Microsoft Azure cloud

❦ 23 novembre 2015 00:28 GMT, Steve McIntyre  : > That's a very good question, and one I'll admit that I'd not paid much > attention to. Unless the images are set up to auto-update at boot (is > that a sensible thing? Do any of the published images do this?) Yes, it is part of

Re: Building cloud images on Debian infrastructure

❦ 1 avril 2016 00:13 +0200, Thomas Goirand  : >> See Riku's talk at DebConf Heidelberg - there are many tools and >> it would be generally better for customized tools to give way to >> generalist tools which can use wrappers or enhancements to provide the >> remaining

Re: Call for Testing: Stretch Cloud Images on AWS

❦ 2 février 2017 21:42 -0800, Noah Meyerhans  : >> overall the image looks fine, no extraneous things, sysctl is clean, >> etc. great job. :) > > Interesting that you bring up sysctl. I consider it a bug that we're > currently running with an unmodified set of sysctl

Re: Building OpenStack images with bootstrap-vz and cloud-init ?

❦ 7 février 2017 15:49 GMT, Jeremy Stanley  : >> This may be true post jessie, but AFAIU, the 'OpenStack' data source isn't >> supported out of the box in Jessie's version of cloud-init (see >> #841315), and one may have to explicitely customize with a change of the >> config

Re: Building OpenStack images with bootstrap-vz and cloud-init ?

❦ 1 février 2017 19:05 +0100, Olivier Berger  : > I have already some basic knowledge of bootstrap-vz, which I've used > with VirtualBox and Vagrant providers, thanks. But I'm wondering whether > anyone documented the specifics of OpenStack. > > Maybe you're

Re: Adding symbolic links for "current" images

❦ 18 novembre 2016 08:02 +0100, Martin Zobel-Helas  : > What i would be willing to accept thought, would be a > /current-8/debian-current-openstack-amd64.qcow2 link which points to the > latest Debian Jessie image. That way people will not need to ajust their > scripts once we

Re: vmdb2: vmdebootstrap rewrite in progress

❦ 29 mars 2017 14:04 +0300, Lars Wirzenius  : > Current status is that it builds a Debian image (assuming you're > running vmdb2 on amd64), but doesn't install a bootloader. My attempts > to get grub-install to work have resulted in my laptop's bootloader > being inadvertently

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

❦ 23 juin 2017 13:46 GMT, Joonas Kylmälä  : > Thank you Vincent for taking a look onto this issue. I identified that > at least these two files enable non-free software: > templates/sources.list.ubuntu.tmpl and > templates/sources.list.debian.tmpl. In Ubuntu's case the

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

Package: cloud-init Version: 0.7.9-2 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi! By default, cloud-init enables the non-free repositories. It shouldn't. I even wonder if this should not be fixed in stable/oldstable too. - -- System Information: Debian Release: 9.0

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

❦ 23 juin 2017 15:13 GMT, Joonas Kylmälä  : > thanks Vincent for the help you gave about creating a patch! The patch > is attached to this email. I'm pretty confident with the modifications > to "sources.list.debian.tmpl" but for "sources.list.ubuntu.tmpl" I would > like

Re: Systemd predictive network interface names for Stretch

❦ 1 juin 2017 11:38 -0700, Zach Marano  : > I haven't found the definitive answer to this question yet. Does Stretch > use predictive network interface names and systemd-networkd by > default? Predicitive network interface names are enabled by default. However,

Re: Systemd predictive network interface names for Stretch

❦ 1 juin 2017 13:23 -0700, Zach Marano  : > So does this mean you still need to hard code the interface names (which > for all intents and purposes may not be static across different hardware) > into /etc/network/interfaces when using predictive network interface names? >

Re: Jessie openstack image updated to version 8.10.3-20180110

❦ 10 janvier 2018 12:05 GMT, Steve McIntyre  : > 8.10.3-20180110 > > Updates in 1 source package(s), 1 binary package(s): > > Source linux-latest, binaries: linux-image-amd64:amd64 > linux-latest (63+deb8u1) jessie-security; urgency=medium > > * Update to 3.16.0-5

Re: Using disk images from cloud.debian.org

❦ 17 novembre 2019 23:40 +01, Johannes Schauer : > As I explained in the first paragraph of my initial email, I'm trying to find > an alternative to creating a bootable disk image myself that I can then use on > salsa CI runners (for example inside autopkgtests). So there is no metadata >

Re: Using disk images from cloud.debian.org

❦ 18 novembre 2019 15:46 +01, Johannes Schauer : > Unfortunately, it doesn't help in my situation because my original problem is > that due to missing functionality (like losetup, mount or kpartx) in the > autopkgtest runners I cannot create disk images so I cannot create a disk > image > of

Re: Debian VM Agent Issue

❦ 2 juin 2020 15:17 +02, Bastian Blank: > [ The original mail was sent to use privately ] > > Hi Jared [...] I think you forgot to put him in copy. Or maybe Bcc? > This is the result if incompatible dependencies in the agent and Gnome. > waagent for now requires ifupdown as the network