Package Details: cloud-init 19.2-1

Git Clone URL: (read-only)
Package Base: cloud-init
Description: The defacto multi-distribution package that handles early initialization of a cloud instance.
Upstream URL:
Licenses: GPL3
Submitter: Barthalion
Maintainer: Sparadox (flaccid)
Last Packager: flaccid
Votes: 4
Popularity: 0.007953
First Submitted: 2018-01-06 19:15
Last Updated: 2019-10-17 05:34

Latest Comments

1 2 3 Next › Last »

flaccid commented on 2019-10-17 05:35

Last issue should be resolved now because startdir usage now removed.

bitfehler commented on 2019-10-14 09:56

@aiM0a then I think you are using the BUILDDIR option in /etc/makepkg.conf?

If you do not use that, the package should build (as a workaround).

aiM0a commented on 2019-10-08 22:55

@bitfehler, no, I get this error building with makepkg -fsircCL.

bitfehler commented on 2019-10-06 18:44

@aiM0a are you building with makechrootpkg? I get the same error when I do, but building does work for me when just using makepkg. See my comment before yours for a link to a patch that fixes the issue.

aiM0a commented on 2019-10-04 14:59

Hello, I'm getting the following error trying to build this package:

install: cannot stat '../': No such file or directory
==> ERROR: A failure occurred in package().

bitfehler commented on 2019-09-09 12:30

Hi, the package in its current form does not build with makechrootpkg. You can find here a commit that fixes that, would be great if you could merge this:

See about the dperecated $startdir mentioned in the commit.

Also, 19.2 is available :)

aberenyi commented on 2019-08-05 14:17

Anyone else getting this AttributeError: 'MIMEMultipart' object has no attribute 'policy' during the init (cloud-init init) stage?

adasauce commented on 2019-07-03 20:00

I think the is a little too opinionated for general use with the defaults set as they are.

I'm maintaining a private fork with defaults that work for my image building process, but IMO maybe leave most of it out and put it on the person installing it to know what they want their cloud-init config to look like post-install and inject the file via whatever config/systems management is being leveraged.

Sparadox commented on 2019-05-28 18:30

@flaccid I just added you to the list.

I'm essentially testing cloud-init to orchestrate Kubernetes cluster components atop AWS and a small French cloud-provider (Scaleway).

That boils down two making sure cloud-init can pull config from the provider's metadata APIs and launch a few systemd units... having a more diverse set of maintainers with various use cases is a very good thing :)

flaccid commented on 2019-05-28 00:55

@bitfehler looks like AUR probably just changed a bit. Assuming python-cheetah3 is the go now.

@Sparadox sure, I can help maintain if you like.