all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Tomáš Čech" <tcech@suse.com>
To: Leo Famulari <leo@famulari.name>
Cc: 25852@debbugs.gnu.org
Subject: bug#25852: Users not updating their installations of Guix
Date: Sun, 5 Mar 2017 08:56:41 +0100	[thread overview]
Message-ID: <20170305075641.76f4mznuod2gztdi@penguin> (raw)
In-Reply-To: <20170304224359.GA18077@jasmine>

[-- Attachment #1: Type: text/plain, Size: 1927 bytes --]

On Sat, Mar 04, 2017 at 05:43:59PM -0500, Leo Famulari wrote:
>On Sat, Mar 04, 2017 at 09:29:41PM +0100, Tomáš Čech wrote:
>> On Thu, Feb 23, 2017 at 04:11:56PM -0500, Leo Famulari wrote:
>> > In my opinion, the recent bug #25775 (Can't install packages after guix
>> > pull) [0] exposed a sort of meta-bug: there are a significant number of
>> > users who were still using the guix-daemon from 0.10.0.
>> >
>> > It seems unlikely that they have been updating all of root's
>> > packages except for the guix package. Rather, I bet they never updated
>> > root's packages at all, for ~1 year.
>> >
>> > I think this is a serious documentation bug.
>>
>> One problem may be that Guix on top of foreign distribution is not
>> able to update itself.
>
>I can update my Guix-on-Debian systems without trouble, using the normal
>`guix pull && guix package -u .` method.

I'm sorry, I meant guix-daemon here.

>> I still offer guix-0.12 RPM package for openSUSE installation as there
>> was no new release. Guix is able to update itself via `guix pull' but
>> it doesn't affect system installation of guix-daemon.
>
>Interesting, I didn't know there was a distro package for openSUSE.

I'm trying to maintain it for quite a long time already... It's part
of distribution (but not on installation medium :)

>For that package, the root user cannot update the guix-daemon?

root user can do anything, but that is not the point here. The point
is that root user interaction is _required_.

I may alter guix-daemon service file to use
/root/.guix-profile/... path that that is also unsafe hack relying
that root user will not break his stuff.

Splitting packages into 2 could be another way to do it, better, quite natural.

And IMHO the best and also "Guix way" could be making guix-daemon aware of
possible newer versions in /gnu/store and execing them instead...

Best regards,

S_W


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-03-05  7:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 21:11 bug#25852: Users not updating their installations of Guix Leo Famulari
2017-02-24  5:42 ` Pjotr Prins
2017-03-02 18:16 ` sirgazil
2017-03-04 20:29 ` Tomáš Čech
2017-03-04 22:43   ` Leo Famulari
2017-03-05  7:56     ` Tomáš Čech [this message]
2017-03-05  9:25       ` Pjotr Prins
2017-03-05  9:43         ` Tomáš Čech
2017-03-06 14:52           ` Ricardo Wurmus
2017-03-07  6:54             ` Pjotr Prins
2017-03-06 21:12 ` Ludovic Courtès
2017-03-06 21:34   ` Leo Famulari
2017-03-07  6:33     ` Tomáš Čech
2017-03-07 19:51       ` Leo Famulari
2017-03-07 20:58         ` Tomáš Čech
2017-03-07 22:22           ` Leo Famulari
2017-03-08  6:25             ` Tomáš Čech
2017-03-08  8:45               ` Leo Famulari
2017-03-08  9:24                 ` Tomáš Čech
2017-03-08 18:15                   ` Leo Famulari
2017-03-09  7:38                     ` Efraim Flashner
2017-03-09 10:58               ` Ludovic Courtès
2017-03-09 12:42                 ` Tomáš Čech
2017-03-09 15:42                   ` Ludovic Courtès
2017-03-07  7:32   ` Mark H Weaver
2017-03-07 10:35     ` Ludovic Courtès
2017-03-11  1:48       ` Mark H Weaver
2017-05-10 13:12         ` Ludovic Courtès
2017-05-10 14:13           ` myglc2
2017-05-10 20:16             ` Ludovic Courtès
2017-05-12  6:06               ` Ricardo Wurmus
2017-05-12  8:29                 ` Ludovic Courtès
2017-05-12 17:10                   ` myglc2

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=20170305075641.76f4mznuod2gztdi@penguin \
    --to=tcech@suse.com \
    --cc=25852@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.