Your message dated Sun, 1 Sep 2019 20:11:42 +0200
with message-id <[email protected]>
and subject line Re: How to proceed
has caused the Debian Bug report #818008,
regarding Make Ansible package configurable.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
818008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818008
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ansible
Version: 2.0.1.0-1
Hi Ansible/Debian maintainers,
I made some changes in the Ansible Debian packaging in order to make it
configurable through debconf. So I added all the stuff like scripts,
templates, ... I also added changelog for version 2.0.1.0-2 with all
details.
Each debconf parameter has default to keep backward compatibility. I
also added a special debconf parameter (ansible/force_overwrite) in
order to force rewrite of /etc/ansible/ansible.cfg if it already exists.
The upstream example still available in /usr/share/doc/ansible/examples
(as defined in Debian packaging policy).
Because I'm newbie in Debian development workflows, I don't know where I
have to make a kind of "pull request". So I put my changes on GitHub
(https://github.com/rmedaer/ansible-debian-pkg). There is currently only
one commit:
https://github.com/rmedaer/ansible-debian-pkg/commit/7fa153bdcc368fad2c3dc8701fe4a8aa73c80d08.
Be my guest if you have any advice or change request to make my changes
"mergeable" to HEAD.
I hope it will help you and the community.
Have a good day,
---
Raphael Medaer
Happy free contributor <[email protected]>
Developer @Escaux <[email protected]>
--- End Message ---
--- Begin Message ---
Closing due to inactivity. Feel free to re-open if you would like to
challenge the assessment below.
On Tue, 16 Oct 2018 15:46:25 +0200 Lee Garrett <[email protected]> wrote:
> Hi Geert, hi Raphael,
>
> personally, I think that the Debian package should stop shipping
> /etc/ansible/{ansible.cfg, hosts} alltogether. The reason is that those files
> have a systemwide affect, and can only be edited by root. The former is
> problematic if you have several projects, in that case you'd just ship a
> ansible.cfg and hosts file within each project. Both those files can be edited
> by the local user. For that reason I think adding debconf questions for that
> is the wrong approach. But if you really want systemwide hosts and ansible
> config, you can still template those with ansible. :)
>
> What are you thoughts on this?
>
> Greets,
> Lee
>
>
>
> On Sun, 14 Oct 2018 14:09:23 +0200 Geert Stappers <[email protected]> wrote:
> >
> > Found today this bugreport (
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818008 )
> > even with a patch.
> >
> > To find out if it stills applies there is now
> > https://salsa.debian.org/stappers/ansible
> > which has branch 'br818008patch'.
> >
> > Difference with
> > https://github.com/rmedaer/ansible-debian-pkg/commit/7fa153bdcc368fad2c3dc8701fe4a8aa73c80d08
> > is that updating debian/changelong is skipped. If all goes well,
> > is @rmedaer the author of the commit.
> >
> >
> > However, the question is what to do next?
> >
> > Would it make sense to have the patch also here in the Debian BTS?
> >
> > Should Ansible be configurable by debconf?
> >
> >
> > Groeten
> > Geert Stappers
> > --
> > Leven en laten leven
> >
> >
>
>
--- End Message ---
