From: Leo Famulari <leo@famulari.name>
To: "Tomáš Čech" <sleep_walker@gnu.org>
Cc: 25852@debbugs.gnu.org
Subject: bug#25852: Users not updating their installations of Guix
Date: Tue, 7 Mar 2017 14:51:18 -0500 [thread overview]
Message-ID: <20170307195118.GA30247@jasmine> (raw)
In-Reply-To: <20170307063330.bhv2ugsvi3qeofu5@penguin>
[-- Attachment #1: Type: text/plain, Size: 1415 bytes --]
On Tue, Mar 07, 2017 at 07:33:30AM +0100, Tomáš Čech wrote:
> On Mon, Mar 06, 2017 at 04:34:34PM -0500, Leo Famulari wrote:
> > On Mon, Mar 06, 2017 at 10:12:21PM +0100, Ludovic Courtès wrote:
> > > Leo Famulari <leo@famulari.name> skribis:
> > >
> > > > 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.
> >
> > They could have been stuck with an old daemon if they copied the systemd
> > or upstart service files we provide.
> >
> > That problem should be fixed by 613d0895b92c677e0639d5e77c55043e38e020c8
> > (build: Don't embed absolute paths in .service and .conf service
> > files.).
>
> That is right. But
>
> 1) there was no release with this "fix"
> 2) I (as distro package maintainer) didn't take this patch manually as
> it is fragile and hacky. Have you considered fresh guix installation?
This will take effect for the next release of Guix; it addresses a
problem that arises when somebody installs the binary release of Guix.
I'm not addressing downstream packages of Guix with this commit.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-07 19:52 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
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 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170307195118.GA30247@jasmine \
--to=leo@famulari.name \
--cc=25852@debbugs.gnu.org \
--cc=sleep_walker@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).