GNU bug report logs -
#52510
guix install - profile build takes forever
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 52510 in the body.
You can then email your comments to 52510 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#52510
; Package
guix
.
(Wed, 15 Dec 2021 13:05:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Florian Hoertlehner <hoertlehner <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Wed, 15 Dec 2021 13:05:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I use guix 1.3, and a simple guix install takes forever. It hangs 2-10
minutes in the profile build phase.
I have a NVME drive, and see 10-80 MB/sec IO Write in this timeframe.
In the terminal I see: "building profile with 159 packages..."
Then I have to wait 5 minutes.
I assume it hard-linking of packages because I use ext4.
this behavior is machine specific. On the machines that are affected it
occurs pretty consistent. But there are exceptions; when I install
a very small new package, the build time sometimes is in the 30 second
range. But typically it takes 5 minutes.
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#52510
; Package
guix
.
(Wed, 15 Dec 2021 13:32:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 52510 <at> debbugs.gnu.org (full text, mbox):
Hi Florian,
Florian Hoertlehner <hoertlehner <at> gmail.com> skribis:
> I use guix 1.3, and a simple guix install takes forever. It hangs 2-10
> minutes in the profile build phase.
> I have a NVME drive, and see 10-80 MB/sec IO Write in this timeframe.
>
> In the terminal I see: "building profile with 159 packages..."
> Then I have to wait 5 minutes.
So it’s really this “building profile” part that takes 5mn, right?
Could you share the output of ‘guix package --export-manifest’ (or ‘guix
package -I’)? You can share it privately if you prefer not to make it
public.
On a 5yo SSD, and with 300+ packages in my profile, this part usually
takes a few seconds. But it could be that for some packages, in
particular packages with lots of propagated inputs, this operation takes
longer.
Thanks,
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#52510
; Package
guix
.
(Sat, 18 Dec 2021 17:26:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 52510 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I use not only guix chan, but nonguix (for the binary build system and for
clojure-tools)
gorilla (for babashka as binary build; I also use it for vs-codium, but
this is currently broken due
to core update merge) I dont think I use repos from guix-science in this
profile.
Generation 151 Dec 18 2021 17:36:46 (current)
gorilla ba6cd01
repository URL: https://github.com/pink-gorilla/gorilla-guix-chan
branch: master
commit: ba6cd01922216e2ac2a34a57f8198a4f76d1255c
science e84cb16
repository URL: https://github.com/guix-science/guix-science.git
branch: master
commit: e84cb167f1f3e2549eae25ec80084cc7253068cf
nonguix 07b206a
repository URL: https://gitlab.com/nonguix/nonguix.git
branch: master
commit: 07b206af5dc32b93cbc6583896d442a87c8d7b22
guix 3aef0e7
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 3aef0e7ee67932058629e45a44091d1b4a322f90
This is the output of "guix package --export-manifest"
;; This "manifest" file can be passed to 'guix package -m' to reproduce
;; the content of your profile. This is "symbolic": it only specifies
;; package names. To reproduce the exact same profile, you also need to
;; capture the channels being used, as returned by "guix describe".
;; See the "Replicating Guix" section in the manual.
(specifications->manifest
(list "calibre"
"hplip"
"rofi"
"readymedia"
"libreoffice"
"emacs"
"ungoogled-chromium"
"nyxt"
"docker"
"qemu"
"virt-manager"
"udiskie"
"remmina"
"claws-mail"
"java-swt"
"openssh"
"syncthing-gtk"
"docker-compose"
"gparted"
"inxi"
"git"
"certbot"
"telegram-desktop"
"quassel"
"xfce4-screenshooter"
"xfce4-notifyd"
"xfce4-whiskermenu-plugin"
"exo"
"fontconfig"
"eovim"
"kate"
"mousepad"
"pdfarranger"
"qpdfview"
"midori"
"nomad"
"vimb"
"glimpse"
"xdot"
"gst-libav"
"gst-plugins-base"
"gst-plugins-good"
"gst-plugins-ugly"
"vlc"
"kodi"
"ffmpeg"
"pavucontrol"
"keepassxc"
"transmission:gui"
"qbittorrent"
"youtube-dl"
"flatpak"
"catfish"
"celestia-gtk"
"elementary-xfce-icon-theme"
"adwaita-icon-theme"
"breeze-icons"
"matcha-theme"
"papirus-icon-theme"
"java-qdox"
"iputils"
"fish"
"byobu"
"ranger"
"mc"
"glances"
"rsync"
"mesa-utils"
"xclock"
"sxiv"
"gstreamer"
"subdl"
"libwebp"
"xdotool"
"ntp"
"xsettingsd"
"node"
"graphviz <at> 2.42"
"font-gnu-freefont"
"emacs-spacemacs-theme"
"icecat"
"syncthing"
"openjdk:jdk"
"clojure-tools"
"gpart"
"wget"
"curl"
"unzip"
"openssl"
"vscodium"
"font-iosevka"
"font-iosevka-aile"
"sdparm"
"hdparm"
"parted"
"cryptsetup"
"cpuid"
"cpuinfo"
"tree"
"whois"
"perftest"
"the-silver-searcher"
"bash"
"zsh"
"zsh-autosuggestions"
"less"
"which"
"grep"
"sed"
"tmux"
"tar"
"p7zip"
"tarlz"
"gzip"
"zip"
"sysfsutils"
"htop"
"ncdu"
"ncurses"
"rclone"
"nano"
"findutils"
"mlocate"
"glibc-locales"
"mcron"
"fasd"
"coreutils"
"hello"
"make"
"gcc-toolchain"
"xcursor-themes"
"hicolor-icon-theme"
"font-hack"
"font-fira-mono"
"font-gnu-unifont"
"font-google-noto"
"font-openmoji"
"opus"
"docker-cli"
"scm"
"go-ipfs"
"arc-icon-theme"
"gnome-icon-theme"
"gnome-backgrounds"
"font-fira-code"
"font-jetbrains-mono"
"font-abattis-cantarell"
"font-dejavu"
"font-liberation"
"font-awesome"
"font-google-material-design-icons"
"gs-fonts"
"font-ibm-plex"
"font-wqy-microhei"
"fastjar"
"rlwrap"
"leiningen"
"babashka"))
On Wed, Dec 15, 2021 at 2:05 PM GNU bug Tracking System <
help-debbugs <at> gnu.org> wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> bug-guix <at> gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 52510 <at> debbugs.gnu.org.
>
> Please do not send mail to help-debbugs <at> gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 52510: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=52510
> GNU Bug Tracking System
> Contact help-debbugs <at> gnu.org with problems
>
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#52510
; Package
guix
.
(Thu, 23 Dec 2021 15:41:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 52510 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
With the merge of core-update-frozen this issue went away. :-)
I hope it does not reappear.
On Wed, Dec 15, 2021 at 2:31 PM Ludovic Courtès <ludo <at> gnu.org> wrote:
> Hi Florian,
>
> Florian Hoertlehner <hoertlehner <at> gmail.com> skribis:
>
> > I use guix 1.3, and a simple guix install takes forever. It hangs 2-10
> > minutes in the profile build phase.
> > I have a NVME drive, and see 10-80 MB/sec IO Write in this timeframe.
> >
> > In the terminal I see: "building profile with 159 packages..."
> > Then I have to wait 5 minutes.
>
> So it’s really this “building profile” part that takes 5mn, right?
>
> Could you share the output of ‘guix package --export-manifest’ (or ‘guix
> package -I’)? You can share it privately if you prefer not to make it
> public.
>
> On a 5yo SSD, and with 300+ packages in my profile, this part usually
> takes a few seconds. But it could be that for some packages, in
> particular packages with lots of propagated inputs, this operation takes
> longer.
>
> Thanks,
> Ludo’.
>
[Message part 2 (text/html, inline)]
Reply sent
to
Leo Famulari <leo <at> famulari.name>
:
You have taken responsibility.
(Thu, 23 Dec 2021 17:38:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Florian Hoertlehner <hoertlehner <at> gmail.com>
:
bug acknowledged by developer.
(Thu, 23 Dec 2021 17:38:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 52510-done <at> debbugs.gnu.org (full text, mbox):
On Thu, Dec 23, 2021 at 04:40:33PM +0100, Florian Hoertlehner wrote:
> With the merge of core-update-frozen this issue went away. :-)
> I hope it does not reappear.
Great! I am closing this bug. Please let us know if it happens again.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#52510
; Package
guix
.
(Tue, 28 Dec 2021 17:43:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 52510 <at> debbugs.gnu.org (full text, mbox):
[desktop-manifest.scm (text/plain, attachment)]
[Message part 2 (text/plain, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 26 Jan 2022 12:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 62 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.