From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: "Fagundes, Paulo" <paulo.fagundes@opengear.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [[meta-virtualization][m-c-s][PATCH]] salt: bump 2018.3 -> 3000
Date: Thu, 27 Feb 2020 17:19:03 -0500 [thread overview]
Message-ID: <20200227221900.GA38669@gmail.com> (raw)
In-Reply-To: <22510.1582580756302855054@lists.yoctoproject.org>
In message: Re: [[meta-virtualization][m-c-s][PATCH]] salt: bump 2018.3 -> 3000
on 24/02/2020 Fagundes, Paulo wrote:
> hey everyone I've uploaded a patch for upgrading salt to the latest v3000
> version (codename: neon)
>
> this patch includes the following changes:
>
> - upgrade to salt 3000
> - use systemd
> - make the set_python_location_hashbang.patch also change from python to
> python3
> - reworked do_install_append()
> - removed the tornado dependency whereas it is now vendored upstream
> - removed most files in the files/ directory whereas those are already present
> in upstream salt/conf and salt/pkg directories
>
> After uploading the patch I've noticed that as a result of the changes in
> do_install_append(), the following config files are no longer installed
> automatically to /etc/salt/
> - cloud
> - roster
> - cloud.conf.d
> - cloud.profiles.d
> - cloud.providers.d
>
> I could add back the above config files and upload a new patch, but I think
> I'll wait on feedback before uploading a new patch.
The update looked fine to me, so I went ahead and merged it. I'd rather
have something in the tree versus iterating on it out of tree.
Cheers,
Bruce
>
> I'd be happy as well if someone else picked up from where I left off :)
>
prev parent reply other threads:[~2020-02-27 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 20:07 [[meta-virtualization][m-c-s][PATCH]] salt: bump 2018.3 -> 3000 Fagundes, Paulo
2020-02-24 21:45 ` Fagundes, Paulo
2020-02-27 22:19 ` Bruce Ashfield [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200227221900.GA38669@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=meta-virtualization@lists.yoctoproject.org \
--cc=paulo.fagundes@opengear.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.