From: 白い熊@相撲道 <guix-devel_gnu.org@sumou.com>
To: Mark H Weaver <mhw@netris.org>
Cc: GuixSD <guix-devel@gnu.org>
Subject: Re: Libreoffice building (sort of)
Date: Wed, 11 Mar 2015 18:32:24 +0100 [thread overview]
Message-ID: <31c4ac58a6a35a5f0aaf774ae6c51062@hcoop.net> (raw)
In-Reply-To: <871tkv1ojp.fsf@netris.org>
On 2015-03-11 17:34, Mark H Weaver wrote:
> What you've done is to roll back your Guix to the 4-month-old version
> of
> Guix that the 'wip-libreoffice' branch was based on.
>
> The proper way would be to use 'git' to rebase that branch on our
> current master branch, and then use that. "guix pull" can't do that.
>
>> I'm asking this as I see a different behavior now
>> with `guix package -d' and `-i' for other packages now than before,
>> and a lot of building from source.
>
> That's probably because Hydra has long ago deleted the binaries from 4
> months ago.
Thanks a lot for this confirmation Mark, I suspected something like this
must have happened when I saw the sourcebuilding...
How best to proceed from here to:
- get back to current master
- keep the built libreoffice in the store
I had an idea that pulling the current master from the downloaded file
will bring me forward again, but doesn't seem it happened - still
building from source.
I don't use Guix from git, this is the GuixSD installed as a clean
system from USB. Is there no other way now than to clone the git guix,
build it an rebase? How will it interact with the GuixSD version of the
tools? Isn't this going to lead to more conflicts? How do I insure the
git guix will take precedende - just make sure to run local commands
only from the git build directory?
Or would maybe now a system reconfigure bring me forward? What is the
cleanest way?
--
白い熊@相撲道
next prev parent reply other threads:[~2015-03-11 17:32 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 21:24 9x15bold xfont 白い熊 @相撲道
2015-03-09 22:03 ` Andreas Enge
2015-03-09 23:57 ` 白い熊 @相撲道
2015-03-10 2:29 ` 宋文武
2015-03-10 8:54 ` Libreoffice building (sort of) 白い熊 @相撲道
2015-03-10 12:06 ` 白い熊 @相撲道
2015-03-10 12:41 ` Ludovic Courtès
2015-03-11 9:01 ` 白い熊@相撲道
2015-03-11 9:27 ` 白い熊@相撲道
2015-03-11 12:04 ` Andreas Enge
2015-03-11 12:34 ` 白い熊@相撲道
2015-03-12 9:22 ` Ludovic Courtès
2015-03-11 16:34 ` Mark H Weaver
2015-03-11 17:32 ` 白い熊@相撲道 [this message]
2015-03-11 19:17 ` Mark H Weaver
2015-03-12 22:56 ` 白い熊@相撲道
2015-03-12 23:10 ` Mark H Weaver
2015-03-12 9:25 ` Merging wip-libreoffice Ludovic Courtès
2015-03-12 9:47 ` Andreas Enge
2015-03-12 14:18 ` Ludovic Courtès
2015-03-10 12:40 ` 9x15bold xfont Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2014-11-24 17:19 Libreoffice building (sort of) John Darrington
2014-11-24 18:03 ` Ludovic Courtès
2014-11-24 19:07 ` John Darrington
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=31c4ac58a6a35a5f0aaf774ae6c51062@hcoop.net \
--to=guix-devel_gnu.org@sumou.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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).