From: sirgazil <sirgazil@zoho.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>, help-guix <help-guix@gnu.org>
Subject: Re: core-updates call for testing
Date: Fri, 24 Apr 2020 18:08:02 +0000 [thread overview]
Message-ID: <171ad600357.c127cae94161.4503436238440610400@zoho.com> (raw)
In-Reply-To: <87eescg8ba.fsf@devup.no>
---- On Fri, 24 Apr 2020 16:25:13 +0000 Marius Bakke <mbakke@fastmail.com> wrote ----
> sirgazil <sirgazil@zoho.com> writes:
>
> > ---- On Fri, 24 Apr 2020 03:20:41 +0000 sirgazil <sirgazil@zoho.com> wrote ----
> > > ---- On Thu, 23 Apr 2020 23:24:23 +0000 Marius Bakke <mbakke@fastmail.com> wrote ----
> > > > Hello Guix!
> > > >
> > > > The "core-updates" branch is ready for testing! According to 'guix
> > > > weather', the substitute coverage is slightly better than on "master"
> > > > for x86_64. You can get it by running:
> > > >
> > > > guix pull --branch=core-updates
> > > >
> > > > Please try upgrading your profiles and systems and file bugs for
> > > > anything that does not work for you. GNOME users in particular are
> > > > encouraged to try the new GNOME 3.34 and report any regressions.
> > >
> > > I pulled from core-updates without problems, but "guix upgrade" failed.
> > >
> > > First, when running "guix upgrade", I got the following message, which I think is confusing because I use GNU, not Guix on a foreign distro:
> > >
> > > $ guix upgrade
> > > guile: warning: failed to install locale
> > > hint: Consider installing the `glibc-utf8-locales' or `glibc-locales' package and defining `GUIX_LOCPATH', along these lines:
> > >
> > > guix package -i glibc-utf8-locales
> > > export GUIX_LOCPATH="$HOME/.guix-profile/lib/locale"
> > >
> > > See the "Application Setup" section in the manual, for more info.
> > >
> > > Then, everything was going alright, until building emacs-guix derivation failed:
> > >
> > > building /gnu/store/6kdl0pyv7i571d6b4vcxskr75ffqw1mk-emacs-guix-0.5.2.drv...
> > > \ 'configure' phasebuilder for `/gnu/store/6kdl0pyv7i571d6b4vcxskr75ffqw1mk-emacs-guix-0.5.2.drv' failed with exit code 1
> > > build of /gnu/store/6kdl0pyv7i571d6b4vcxskr75ffqw1mk-emacs-guix-0.5.2.drv failed
> > > View build log at '/var/log/guix/drvs/6k/dl0pyv7i571d6b4vcxskr75ffqw1mk-emacs-guix-0.5.2.drv.bz2'.
> > > guix upgrade: error: build of `/gnu/store/6kdl0pyv7i571d6b4vcxskr75ffqw1mk-emacs-guix-0.5.2.drv' failed
> > >
> > >
> > > The build log said:
> > >
> > > starting phase `configure'
> > > source directory: "/tmp/guix-build-emacs-guix-0.5.2.drv-0/emacs-guix-0.5.2" (relative from build: ".")
> > > build directory: "/tmp/guix-build-emacs-guix-0.5.2.drv-0/emacs-guix-0.5.2"
> > > configure flags: ("CONFIG_SHELL=/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "SHELL=/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "--prefix=/gnu/store/bqplgazij77awh62579p56wbnxdb1c2l-emacs-guix-0.5.2" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu")
> > > configure: WARNING: unrecognized options: --enable-fast-install
> > > checking for a BSD-compatible install... /gnu/store/57xj5gcy1jbl9ai2lnrqnpr0dald9i65-coreutils-8.32/bin/install -c
> > > checking whether build environment is sane... yes
> > > checking for a thread-safe mkdir -p... /gnu/store/57xj5gcy1jbl9ai2lnrqnpr0dald9i65-coreutils-8.32/bin/mkdir -p
> > > checking for gawk... gawk
> > > checking whether make sets $(MAKE)... no
> > > checking whether make supports nested variables... yes
> > > checking whether make supports nested variables... (cached) yes
> > > checking for pkg-config... /gnu/store/krpyb0zi700dcrg9cc8932w4v0qivdg9-pkg-config-0.29.2/bin/pkg-config
> > > checking pkg-config is at least version 0.9.0... yes
> > > configure: checking for guile 2.2
> > > configure: checking for guile 2.0
> > > configure: error:
> > > No Guile development packages were found.
> > >
> > > Please verify that you have Guile installed. If you installed Guile
> > > from a binary distribution, please verify that you have also installed
> > > the development packages. If you installed it yourself, you might need
> > > to adjust your PKG_CONFIG_PATH; see the pkg-config man page for more.
> > >
> > > command "/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "./configure" "CONFIG_SHELL=/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "SHELL=/gnu/store/pwcp239kjf7lnj5i4lkdzcfcxwcfyk72-bash-minimal-5.0.16/bin/bash" "--prefix=/gnu/store/bqplgazij77awh62579p56wbnxdb1c2l-emacs-guix-0.5.2" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" failed with status 1
> > >
> > >
> >
> >
> > Then, I decided to remove emacs-guix, and try again to upgrade. This time, one of my packages in a custom channel failed with "no code for (term ansi-color)" (the package definition: https://gitlab.com/sirgazil/guix-channel-x/-/blob/master/sirgazil-x/packages/guile.scm#L13). This is not a new package in my profile, I've been using it for a long time. Since both error seemed to be related to Guile, I removed all Guile-related packages from my profile and tried upgrading again. This time, the upgrade succeeded.
>
> Thanks for testing! I fixed the emacs-guix issue in commit
> f568581c2bfb3a7367442c9ccc23613c43f6f1e9 plus some related changes in
> 962554ddcf86675362486a683acd94863ba68d8a and
> 9b42918edd3f7e9d505c874d3947c0a0815fe551.
It failed again, though: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=40824
next prev parent reply other threads:[~2020-04-24 18:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 23:24 core-updates call for testing Marius Bakke
2020-04-24 3:20 ` sirgazil
2020-04-24 12:58 ` sirgazil
2020-04-24 16:25 ` Marius Bakke
2020-04-24 16:54 ` Gábor Boskovits
2020-04-24 19:29 ` sirgazil
2020-04-24 18:08 ` sirgazil [this message]
2020-04-24 21:52 ` Marius Bakke
2020-04-24 22:42 ` sirgazil
2020-04-24 18:46 ` sirgazil
2020-04-24 14:40 ` Jack Hill
2020-04-24 20:06 ` Jack Hill
2020-04-25 3:02 ` Jack Hill
2020-04-25 13:24 ` sirgazil
2020-04-25 18:13 ` sirgazil
2020-04-29 11:31 ` Ricardo Wurmus
2020-04-25 18:36 ` sirgazil
2020-04-25 21:19 ` Jack Hill
2020-04-25 21:54 ` sirgazil
2020-04-27 22:09 ` Jack Hill
2020-04-29 6:17 ` Ricardo Wurmus
2020-04-25 18:06 ` Leo Famulari
2020-04-28 13:17 ` Marius Bakke
2020-04-28 12:46 ` Efraim Flashner
2020-04-28 13:12 ` Marius Bakke
2020-05-04 14:51 ` Timothy Sample
2020-05-04 15:32 ` Marius Bakke
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=171ad600357.c127cae94161.4503436238440610400@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=mbakke@fastmail.com \
/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.
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).