Tell users to update/reconfigure regularly

  • Done
  • quality assurance status badge
Details
3 participants
  • Jesse Gibbons
  • Ludovic Courtès
  • pelzflorian (Florian Pelz)
Owner
unassigned
Submitted by
pelzflorian (Florian Pelz)
Severity
normal
P
P
pelzflorian (Florian Pelz) wrote on 13 Jul 2019 11:35
(address . bug-guix@gnu.org)
20190713093530.eph5xvkqyhejkodd@pelzflorian.localdomain
When installing Guix System from the iso image, users should be told
to pull and reconfigure regularly. Even though it is mentioned in the
manual, not everyone reads manuals. I believe Guix’ target users
include inexperienced users who do not know that they should update
and upgrade regularly. Therefore the installer should tell users how
to do so and that it is important and perhaps what to do if things
break.

Of course, some users still won’t update and they should have the
liberty to decide for themselves, but some users just forget to
update. Ubuntu defaults to automatic updates, which slow down the
machine and annoy users. Still, maybe there should be notifications
like a cron job invoking libnotify’s notify-send.

Regards,
Florian
L
L
Ludovic Courtès wrote on 14 Jul 2019 16:59
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)(address . 36636@debbugs.gnu.org)
874l3o1x2z.fsf@gnu.org
Hello,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

Toggle quote (8 lines)
> When installing Guix System from the iso image, users should be told
> to pull and reconfigure regularly. Even though it is mentioned in the
> manual, not everyone reads manuals. I believe Guix’ target users
> include inexperienced users who do not know that they should update
> and upgrade regularly. Therefore the installer should tell users how
> to do so and that it is important and perhaps what to do if things
> break.

The ‘guix’ command itself tells you to do so. But of course, if you
never run ‘guix’, you never see that message.

Toggle quote (6 lines)
> Of course, some users still won’t update and they should have the
> liberty to decide for themselves, but some users just forget to
> update. Ubuntu defaults to automatic updates, which slow down the
> machine and annoy users. Still, maybe there should be notifications
> like a cron job invoking libnotify’s notify-send.

Sounds like something we can do.

Ultimately though, what can we do for users who do not read the manual
and do not run ‘guix’ either? Would a notification really help?

Longer-term I think we should have an unattended upgrade service, and it
should probably be part of ‘%desktop-services’.

Thoughts?

Ludo’.
P
P
pelzflorian (Florian Pelz) wrote on 14 Jul 2019 18:36
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 36636@debbugs.gnu.org)
20190714163645.wbvsvxyin43hmjqj@pelzflorian.localdomain
Yes, you are right that unattended upgrades are a more responsible
default than a notification cron job. Unattended upgrades would
resolve this issue. Should an unattended upgrades service be added to
Guix’ list of longer-term todos and this bug be closed?

Regards,
Florian
J
J
Jesse Gibbons wrote on 14 Jul 2019 21:19
(address . bug-guix@gnu.org)
20190714131942.12650abd@gmail.com
On Sun, 14 Jul 2019 18:36:45 +0200
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:

Toggle quote (11 lines)
> Yes, you are right that unattended upgrades are a more responsible
> default than a notification cron job. Unattended upgrades would
> resolve this issue. Should an unattended upgrades service be added to
> Guix’ list of longer-term todos and this bug be closed?
>
> Regards,
> Florian
>
>
>

How often would the job be run by default? Daily? Weekly? I presume it
would be configurable to run more or less often.
L
L
Ludovic Courtès wrote on 15 Jul 2019 11:13
(name . pelzflorian (Florian Pelz))(address . pelzflorian@pelzflorian.de)(address . 36636@debbugs.gnu.org)
87tvbnr77j.fsf@gnu.org
Hello,

"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:

Toggle quote (5 lines)
> Yes, you are right that unattended upgrades are a more responsible
> default than a notification cron job. Unattended upgrades would
> resolve this issue. Should an unattended upgrades service be added to
> Guix’ list of longer-term todos and this bug be closed?

It’d be great if you could open an issue for unattended upgrades (it
could be implemented anytime, it’s not a long-term task), and close this
one.

Thanks,
Ludo’.
P
P
pelzflorian (Florian Pelz) wrote on 15 Jul 2019 12:39
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 36636-done@debbugs.gnu.org)
20190715103938.k7lwao24n2mmwkvw@pelzflorian.localdomain
On Mon, Jul 15, 2019 at 11:13:36AM +0200, Ludovic Courtès wrote:
Toggle quote (7 lines)
> It’d be great if you could open an issue for unattended upgrades (it
> could be implemented anytime, it’s not a long-term task), and close this
> one.
>
> Thanks,
> Ludo’.


Closing.

Regards,
Florian
Closed
L
L
Ludovic Courtès wrote on 15 Jul 2019 14:33
(name . Jesse Gibbons)(address . jgibbons2357@gmail.com)(address . 36636@debbugs.gnu.org)
87d0ibo4ss.fsf@gnu.org
Jesse Gibbons <jgibbons2357@gmail.com> skribis:

Toggle quote (3 lines)
> How often would the job be run by default? Daily? Weekly? I presume it
> would be configurable to run more or less often.

It should definitely be configurable.

Ludo’.
?
Your comment

This issue is archived.

To comment on this conversation send an email to 36636@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 36636
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch