On Thu, Apr 17, 2014 at 4:57 AM, Petter Reinholdtsen wrote:
> [Jonas Smedegaard]
>> Seems to me that you are basically arguing that debconf in its
>> current form only legally works on initial install and interactively
>> by admins - not as automated reconfiguration by other
[James Valleroy]
I think we can use dpkg-reconfigure without the interactive frontend:
echo jwchat jwchat/ApacheServerName string $hostname |
debconf-set-selections
DEBIAN_FRONTEND=noninteractive dpkg-reconfigure jwchat
Do you see any issues with this approach?
[Jonas Smedegaard]
Well,
Quoting Petter Reinholdtsen (2014-04-17 08:20:22)
[James Valleroy]
I think we can use dpkg-reconfigure without the interactive frontend:
echo jwchat jwchat/ApacheServerName string $hostname |
debconf-set-selections
DEBIAN_FRONTEND=noninteractive dpkg-reconfigure jwchat
Do you see any
[Jonas Smedegaard]
Seems to me that you are basically arguing that debconf in its
current form only legally works on initial install and interactively
by admins - not as automated reconfiguration by other packages.
Is that correctly understood?
Almost. The current tool set have those
Quoting Petter Reinholdtsen (2014-04-17 08:20:22)
[James Valleroy]
I think we can use dpkg-reconfigure without the interactive frontend:
echo jwchat jwchat/ApacheServerName string $hostname |
debconf-set-selections
DEBIAN_FRONTEND=noninteractive dpkg-reconfigure jwchat
Do you see
Jag
Den 17 apr 2014 11:25 skrev Jonas Smedegaard d...@jones.dk:
Quoting Petter Reinholdtsen (2014-04-17 08:20:22)
[James Valleroy]
I think we can use dpkg-reconfigure without the interactive frontend:
echo jwchat jwchat/ApacheServerName string $hostname |
debconf-set-selections
Quoting Anders Jackson (2014-04-17 13:14:56)
Den 17 apr 2014 11:25 skrev Jonas Smedegaard [1]d...@jones.dk:
Quoting Petter Reinholdtsen (2014-04-17 08:20:22)
If that work, jwchat is broken,
[snip]
Ahh, now I realize what your point is: Declaring and applying must be
done together - so as to
2014-04-17 14:19 GMT+02:00 Jonas Smedegaard d...@jones.dk:
Quoting Anders Jackson (2014-04-17 13:14:56)
Den 17 apr 2014 11:25 skrev Jonas Smedegaard [1]d...@jones.dk:
Quoting Petter Reinholdtsen (2014-04-17 08:20:22)
If that work, jwchat is broken,
[snip]
Ahh, now I realize what your point
Quoting Anders Jackson (2014-04-17 23:51:30)
2014-04-17 14:19 GMT+02:00 Jonas Smedegaard d...@jones.dk:
Quoting Anders Jackson (2014-04-17 13:14:56)
Den 17 apr 2014 11:25 skrev Jonas Smedegaard [1]d...@jones.dk:
Quoting Petter Reinholdtsen (2014-04-17 08:20:22)
If that work, jwchat is broken,
Quoting Nick Daly (2014-04-16 01:08:20)
Jonas Smedegaard d...@jones.dk writes:
When Plinth directly edits configuration files, it is an
administrators' tool.
Solution is to have Plinth only ever communicate with debconf!
...and convince various package maintainers (e.g. by offering
[Jonas Smedegaard]
Good point!
James created a wiki page tracking transition to debconf, and I have now
referenced from that page a tutorial on packaging with debconf:
https://wiki.debian.org/FreedomBox/Build/DebconfConfig
I noticed you added this:
NB! Debconf is preferred over
Quoting Petter Reinholdtsen (2014-04-16 10:54:56)
can you add some details to the page on how the freedombox project can
use debconf to change the setup we apply to packages after
installation? For example, if the tor package started using debconf
and we used debconf to configure tor
On Tuesday 15 April 2014 03:35 AM, Jonas Smedegaard wrote:
[...]
When Plinth directly edits configuration files, it is an administrators'
tool.
Solution is to have Plinth only ever communicate with debconf!
I can see that many uses cases for configuration can be done in this
manner.
Quoting Sunil Mohan (2014-04-16 20:12:33)
On Tuesday 15 April 2014 03:35 AM, Jonas Smedegaard wrote:
[...]
When Plinth directly edits configuration files, it is an
administrators' tool.
Solution is to have Plinth only ever communicate with debconf!
I can see that many uses cases for
On Wed, Apr 16, 2014 at 8:04 AM, Jonas Smedegaard d...@jones.dk wrote:
Quoting Petter Reinholdtsen (2014-04-16 10:54:56)
can you add some details to the page on how the freedombox project can
use debconf to change the setup we apply to packages after
installation? For example, if the tor
Quoting James Valleroy (2014-04-17 02:39:13)
On Wed, Apr 16, 2014 at 8:04 AM, Jonas Smedegaard d...@jones.dk wrote:
Second is specific to Plinth, and should be documented in manpages
of debconf. For an equivalent implemented in shell it would involve
debconf-set-selections and debconf
[Jonas Smedegaard]
I have written several times about that very issue on this list.
Here's an early example (few months after birth of the list):
Glad to have your voice here, and suspect we are getting to a point
where more contributors understand what you mean.
[Jonas Smedegaard 2010-09-01
Quoting Petter Reinholdtsen (2014-04-15 08:24:20)
[Jonas Smedegaard 2010-09-01 13:07:45]
I strongly recommend FreedomBox to be a Debian thing, rather than an
on-top-of-Debian thing. I.e. *not* act on configfiles from a sysadmin
point of view but as part of Debian, obeying Debian Policy which
Jonas Smedegaard d...@jones.dk writes:
When Plinth directly edits configuration files, it is an administrators'
tool.
Solution is to have Plinth only ever communicate with debconf!
...and convince various package maintainers (e.g. by offering patches)
to implement via debconf the
Hi all,
I added a new wiki page here:
https://wiki.debian.org/FreedomBox/Build/DebconfConfig
It's a table listing the packages that own config files which are
currently being modified by scripts in freedombox-setup or plinth.
Hope this will be useful for tracking our progress. Feel free to add
Quoting Petter Reinholdtsen (2014-04-14 22:41:30)
I've been running an old freedombox image for a while, and upgraded it
regularly, and so far I have seen two conffile questions, one for
/etc/dnsmasq.conf and another for /etc/tor/torrc. I assume upgrades
should be handled using the plinth
21 matches
Mail list logo