bug#46782:
There is a similar issue that is solved: https://issues.guix.gnu.org/59425
bug#59425: guix shell --container fails to mount host filesystem
Nice! That runs. Thank you. I will upgrade my guix. Le mer. 23 nov. 2022 à 15:03, Ludovic Courtès a écrit : > Hi, > > bbb ee skribis: > > > dev_1@dev_1 /mnt/recoverData$ guix shell --container coreutils -- echo > Elmo > > guix shell: error: mount: mount "/mnt/recoverData" on > > "/tmp/guix-directory.ut68VE//mnt/recoverData": Invalid argument > > ``` > > > > ## environment > > ``` > > $ uname -a > > Linux dev_1 5.18.18 #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux > > $ guix describe > > Generation 9 Oct 22 2022 16:05:50 (current) > > guix 85aff4d > > repository URL: https://git.savannah.gnu.org/git/guix.git > > branch: master > > commit: 85aff4de30686359ffb50845eb0930c0a18dc8ba > > > I believe this was fixed in commit > c585b4bc68813a351d6a87d19b9adf4041506355, see > <https://issues.guix.gnu.org/59185>. > > Could you check something like: > > guix time-machine --commit=c585b4bc68813a351d6a87d19b9adf4041506355 -- \ > shell -C coreutils > > ? > > Thanks in advance, > Ludo’. >
bug#59425: guix can't mount mountpoint path, and the home path.
The new tests show guix can mount all path except mountpoint path, and the home path. ``` dev_1@dev_1 /mnt/recoverData$ mountpoint . ; guix shell --container coreutils -- echo Elmo . is a mountpoint guix shell: error: mount: mount "/mnt/recoverData" on "/tmp/guix-directory.Fu8aV9//mnt/recoverData": Invalid argument dev_1@dev_1 /mnt/recoverData/borg_restore$ mountpoint . ; guix shell --container coreutils -- echo Elmo . is not a mountpoint Elmo dev_1@dev_1 ~$ mountpoint . ; guix shell --container coreutils -- echo Elmo . is not a mountpoint guix shell: error: mount: mount "/home/dev_1" on "/tmp/guix-directory.shXxIg//home/dev_1": Invalid argument dev_1@dev_1 ~/Downloads$ mountpoint . ; guix shell --container coreutils -- echo Elmo . is not a mountpoint Elmo ```
bug#59425: only dir which realpath is in /tmp is mountalbe
If I access a unmountable dir from /tmp using symlink, I still can't monnt it: ``` dev_1@dev_1 /tmp$ ln -s ~ . dev_1@dev_1 /tmp$ cd dev_1 dev_1@dev_1 /tmp/dev_1$ df . Filesystem 1K-blocks Used Available Use% Mounted on /dev/nvme0n1p7 209921236 180796556 19661028 91% / dev_1@dev_1 /tmp/dev_1$ guix shell --container coreutils -- echo Elmo guix shell: error: mount: mount "/home/dev_1" on "/tmp/guix-directory.X9jW4K//home/dev_1": Invalid argument dev_1@dev_1 /tmp/dev_1$ realpath /tmp/dev_1 /home/dev_1 ``` So not all subdir of /tmp is mountable, only dir which realpath is in /tmp is mountalbe
bug#59425: guix shell --container fails to mount host filesystem
## description guix shell --container can only mount subdir in /tmp, and fail for all other dir: ``` # success mount in all subdir of /tmp dev_1@dev_1 /tmp/test2$ df . Filesystem 1K-blocks Used Available Use% Mounted on /dev/nvme0n1p7 209921236 180793652 19663932 91% / dev_1@dev_1 /tmp/test2$ guix shell --container coreutils -- echo Elmo Elmo dev_1@dev_1 /tmp/test2$ cd /tmp/ dev_1@dev_1 /tmp$ df . Filesystem 1K-blocks Used Available Use% Mounted on /dev/nvme0n1p7 209921236 180793720 19663864 91% / dev_1@dev_1 /tmp$ guix shell --container coreutils -- echo Elmo Elmo # fail for all other dir dev_1@dev_1 /tmp$ cd / dev_1@dev_1 /$ df . Filesystem 1K-blocks Used Available Use% Mounted on /dev/nvme0n1p7 209921236 180793808 19663776 91% / dev_1@dev_1 /$ guix shell --container coreutils -- echo Elmo guix shell: error: mount: mount "/" on "/tmp/guix-directory.fKcwvT//": Invalid argument dev_1@dev_1 /mnt/recoverData$ cd ~ dev_1@dev_1 ~$ df . Filesystem 1K-blocks Used Available Use% Mounted on /dev/nvme0n1p7 209921236 180793732 19663852 91% / dev_1@dev_1 ~$ guix shell --container coreutils -- echo Elmo guix shell: error: mount: mount "/home/dev_1" on "/tmp/guix-directory.LUuYdU//home/dev_1": Invalid argument # Other partition is also no mountable: dev_1@dev_1 /mnt$ cd recoverData/ dev_1@dev_1 /mnt/recoverData$ df . Filesystem 1K-blocks Used Available Use% Mounted on /dev/nvme0n1p8 122503676 91394804 25287412 79% /mnt/recoverData dev_1@dev_1 /mnt/recoverData$ guix shell --container coreutils -- echo Elmo guix shell: error: mount: mount "/mnt/recoverData" on "/tmp/guix-directory.ut68VE//mnt/recoverData": Invalid argument ``` ## environment ``` $ uname -a Linux dev_1 5.18.18 #1 SMP PREEMPT_DYNAMIC 1 x86_64 GNU/Linux $ guix describe Generation 9 Oct 22 2022 16:05:50 (current) guix 85aff4d repository URL: https://git.savannah.gnu.org/git/guix.git branch: master commit: 85aff4de30686359ffb50845eb0930c0a18dc8ba nonguix 3f00d57 repository URL: https://gitlab.com/nonguix/nonguix branch: master commit: 3f00d57adce5d0a185708fd5c7c5ff6f852c2bf7 ``` ## similar issue: https://issues.guix.gnu.org/46782
bug#59278: how gcc-toolchain can depends a package who doesn't exists?
In the documentation, when it says "guix search" search matching package, if users don't find a package defined in .scm (hidden or no), users can consider it is a bug, because that doesn't match the behavior described in the specification (here, the manual and "guix search --help"). Le mar. 15 nov. 2022 à 15:54, zimoun a écrit : > Hi, > > On Tue, 15 Nov 2022 at 00:53, bbb ee wrote: > > > in commit c81457, how gcc-toolchain can depends a package who doesn't > > exists? > > The package exists, it is ’hidden’ – it means not accessible at the CLI > level. The ’inherit’ copies, so gcc-11 is also hidden, for instance. > > --8<---cut here---start->8--- > (define-public gcc-4.7 > [...] > (hidden-package > (package >(name "gcc") >(version "4.7.4") > > (define-public gcc-4.8 > (package (inherit gcc-4.7) > (version "4.8.5") > > [...] > > (define-public gcc-11 > (package >(inherit gcc-8) >(version "11.3.0") > --8<---cut here---end--->8--- > > The package ’gcc’ by itself is not barely useful because you also need > linker etc. Well, you usually need a complete toolchain, named > gcc-toolchain. ;-) > > See manual: < > https://guix.gnu.org/manual/devel/en/guix.html#The-GCC-toolchain> > > > So this is not a bug and I miss how what could be improved. Closing? > > Cheers, > simon >
bug#59278: how gcc-toolchain can depends a package who doesn't exists?
It is just a little confusing for newcomers to guix. If we really want to improve something, I think that could be to give a more rigorous specification of the guix command: in `guix search --help`, the documentation could be "Search for no hidden packages matching REGEXPS." in https://guix.gnu.org/manual/en/html_node/Invoking-guix-package.html#Invoking-guix-package, in the specification of the option -s : "-s regexp List the available packages whose name, synopsis, or description matches regexp " What exactly means "available" ? For example, available means no hidden guix package. And in Le mar. 15 nov. 2022 à 15:54, zimoun a écrit : > Hi, > > On Tue, 15 Nov 2022 at 00:53, bbb ee wrote: > > > in commit c81457, how gcc-toolchain can depends a package who doesn't > > exists? > > The package exists, it is ’hidden’ – it means not accessible at the CLI > level. The ’inherit’ copies, so gcc-11 is also hidden, for instance. > > --8<---cut here---start->8--- > (define-public gcc-4.7 > [...] > (hidden-package > (package >(name "gcc") >(version "4.7.4") > > (define-public gcc-4.8 > (package (inherit gcc-4.7) > (version "4.8.5") > > [...] > > (define-public gcc-11 > (package >(inherit gcc-8) >(version "11.3.0") > --8<---cut here---end--->8--- > > The package ’gcc’ by itself is not barely useful because you also need > linker etc. Well, you usually need a complete toolchain, named > gcc-toolchain. ;-) > > See manual: < > https://guix.gnu.org/manual/devel/en/guix.html#The-GCC-toolchain> > > > So this is not a bug and I miss how what could be improved. Closing? > > Cheers, > simon >
bug#59278:
close #59278
bug#59278: how gcc-toolchain can depends a package who doesn't exists?
Thanks, I close the issue Le mar. 15 nov. 2022 à 07:27, Julien Lepiller a écrit : > Hi, > > This is not a bug. The gcc package exists, but is hidden from CLI on > purpose because you shouldn't install it and use it directly. You should > use gcc-toolchain instead. > > Le 15 novembre 2022 00:53:32 GMT+01:00, bbb ee a > écrit : >> >> in version c81457a5883ea43950eb2ecdcbb58a5b144bcd11 of guix, >> gcc-toolchain depends gcc: >> ``` >> $ DEFAULT_CHANNELS=/tmp/default_channels.scm >> $ echo "%default-channels" > $DEFAULT_CHANNELS >> # I force guix to use only %default-channels here >> $ guix time-machine --commit=c81457a5883ea43950eb2ecdcbb58a5b144bcd11 -C >> $DEFAULT_CHANNELS -- search gcc-toolchain >> guile: warning: failed to install locale >> name: gcc-toolchain >> version: 9.3.0 >> outputs: out debug static >> systems: x86_64-linux i686-linux >> dependencies: binutils@2.32 gcc@9.3.0 glibc@2.29 ld-wrapper@0 >> ``` >> >> >> However, I can't find gcc package in this version of guix >> ``` >> $ guix time-machine --commit=c81457a5883ea43950eb2ecdcbb58a5b144bcd11 -C >> $DEFAULT_CHANNELS -- search gcc >> # no found gcc >> >> # guix install failure message confirm that gcc doesn't exist in commit >> c81457 >> $ guix time-machine --commit=c81457a5883ea43950eb2ecdcbb58a5b144bcd11 -C >> $DEFAULT_CHANNELS -- install gcc -p ~/opt/python-dev_3_7 >> guile: warning: failed to install locale >> guix install: error: gcc: unknown package >> ``` >> >> in commit c81457, how gcc-toolchain can depends a package who doesn't >> exists? >> >
bug#59278: how gcc-toolchain can depends a package who doesn't exists?
in version c81457a5883ea43950eb2ecdcbb58a5b144bcd11 of guix, gcc-toolchain depends gcc: ``` $ DEFAULT_CHANNELS=/tmp/default_channels.scm $ echo "%default-channels" > $DEFAULT_CHANNELS # I force guix to use only %default-channels here $ guix time-machine --commit=c81457a5883ea43950eb2ecdcbb58a5b144bcd11 -C $DEFAULT_CHANNELS -- search gcc-toolchain guile: warning: failed to install locale name: gcc-toolchain version: 9.3.0 outputs: out debug static systems: x86_64-linux i686-linux dependencies: binutils@2.32 gcc@9.3.0 glibc@2.29 ld-wrapper@0 ``` However, I can't find gcc package in this version of guix ``` $ guix time-machine --commit=c81457a5883ea43950eb2ecdcbb58a5b144bcd11 -C $DEFAULT_CHANNELS -- search gcc # no found gcc # guix install failure message confirm that gcc doesn't exist in commit c81457 $ guix time-machine --commit=c81457a5883ea43950eb2ecdcbb58a5b144bcd11 -C $DEFAULT_CHANNELS -- install gcc -p ~/opt/python-dev_3_7 guile: warning: failed to install locale guix install: error: gcc: unknown package ``` in commit c81457, how gcc-toolchain can depends a package who doesn't exists?
bug#56371: Can't remove a package present in profil
Thanks, it is done :) Le ven. 8 juil. 2022 à 09:13, ( a écrit : > > Control: close #56371 > > To run a control command, send it to cont...@debbugs.gnu.org :) > > -- ( >
bug#56371: Can't remove a package present in profil
close #56371 Le mar. 5 juil. 2022 à 12:46, bbb ee a écrit : > Thanks for the tip! > > Le lun. 4 juil. 2022 à 07:04, Julien Lepiller a > écrit : > >> It's not a bug, because you don't have icedtea in your profile, but >> icedtea:jdk. Guix is picky with outputs. Try "guix remove icedtea:jdk" :) >> >> On July 3, 2022 7:25:46 PM GMT+02:00, bbb ee wrote: >>> >>> Hi, >>> >>> I have icedtea installed in my current profil, but `guix package remove` >>> doesn't find it. >>> ``` >>> $ guix package -p ~/.guix-profile -I | grep icedtea >>> icedtea 3.19.0 jdk >>> /gnu/store/5k7lsz61p8fq37c9x5p9xalryjxk31bs-icedtea-3.19.0-jdk >>> $ guix package -p ~/.guix-profile -r icedtea >>> guix package: error: package 'icedtea' not found in profile >>> ``` >>> >>> It is a bug? >>> >>
bug#56371: Can't remove a package present in profil
Control: close #56371 Le mar. 5 juil. 2022 à 12:46, bbb ee a écrit : > close #56371 > > Le mar. 5 juil. 2022 à 12:46, bbb ee a écrit : > >> Thanks for the tip! >> >> Le lun. 4 juil. 2022 à 07:04, Julien Lepiller a >> écrit : >> >>> It's not a bug, because you don't have icedtea in your profile, but >>> icedtea:jdk. Guix is picky with outputs. Try "guix remove icedtea:jdk" :) >>> >>> On July 3, 2022 7:25:46 PM GMT+02:00, bbb ee wrote: >>>> >>>> Hi, >>>> >>>> I have icedtea installed in my current profil, but `guix package >>>> remove` doesn't find it. >>>> ``` >>>> $ guix package -p ~/.guix-profile -I | grep icedtea >>>> icedtea 3.19.0 jdk >>>> /gnu/store/5k7lsz61p8fq37c9x5p9xalryjxk31bs-icedtea-3.19.0-jdk >>>> $ guix package -p ~/.guix-profile -r icedtea >>>> guix package: error: package 'icedtea' not found in profile >>>> ``` >>>> >>>> It is a bug? >>>> >>>
bug#56371: Can't remove a package present in profil
Thanks for the tip! Le lun. 4 juil. 2022 à 07:04, Julien Lepiller a écrit : > It's not a bug, because you don't have icedtea in your profile, but > icedtea:jdk. Guix is picky with outputs. Try "guix remove icedtea:jdk" :) > > On July 3, 2022 7:25:46 PM GMT+02:00, bbb ee wrote: >> >> Hi, >> >> I have icedtea installed in my current profil, but `guix package remove` >> doesn't find it. >> ``` >> $ guix package -p ~/.guix-profile -I | grep icedtea >> icedtea 3.19.0 jdk >> /gnu/store/5k7lsz61p8fq37c9x5p9xalryjxk31bs-icedtea-3.19.0-jdk >> $ guix package -p ~/.guix-profile -r icedtea >> guix package: error: package 'icedtea' not found in profile >> ``` >> >> It is a bug? >> >
bug#56371: Can't remove a package present in profil
Hi, I have icedtea installed in my current profil, but `guix package remove` doesn't find it. ``` $ guix package -p ~/.guix-profile -I | grep icedtea icedtea 3.19.0 jdk /gnu/store/5k7lsz61p8fq37c9x5p9xalryjxk31bs-icedtea-3.19.0-jdk $ guix package -p ~/.guix-profile -r icedtea guix package: error: package 'icedtea' not found in profile ``` It is a bug?
bug#52836: "guix import pypi" fails with "Failed to extract file from wheel" and "no requires.txt file found"
> Is it a bug on Guix side or upstream? Because it seems that upstream > does not provide metadata information, at least, as usually expected. `pip install PyPortfolioOpt`, `poetry add PyPortfolioOpt` runs for me. If other python package installer can run, I suppose the upstream is correct. Unless Guix is not as powerful as other python package installers, and cannot work for certain type of PyPi packages. In this case, can this be considered an improvement to be made? Le mer. 29 déc. 2021 à 18:09, zimoun a écrit : > Hi, > > On Mon, 27 Dec 2021 at 22:10, bbb ee wrote: > > > ``` > > guix import: warning: Failed to extract file: > > PyPortfolioOpt-1.5.1.dist-info/METADATA from wheel. > > guix import: warning: Cannot guess requirements from source archive: no > > requires.txt file found. > > ``` > > Is it a bug on Guix side or upstream? Because it seems that upstream > does not provide metadata information, at least, as usually expected. > > Well, I have not yet inspected the PyPI package but it seems possible > that it is incorrectly packaged with the Setuptools standard. > > > > ## additional information > > This user has encountered a similar issue for "guix import pypi httpie" > > https://www.mail-archive.com/bug-guix@gnu.org/msg14277.html > > > > However "guix import pypi httpie" runs for my version of guix. > > Well, “guix import pypi httpie” works for me. > > > Cheers, > simon >
bug#52002: missing $GUIX_PROFILE/share/emacs/site-lisp in EMACSLOADPATH
Thanks, the problem is solved.
## Possible cause
Initially, I have emacs installed and ~/.guix-profile/etc/profile sourced.
but when I type "guix package -I | grep emacs". I don't see emacs package
(strange).
So I reinstall emacs : guix install emacs. Then I can see 2 emacs-27.1
installation
```
$ which -a emacs
/home/dev_1/.guix-profile/bin/emacs
/home/dev_1/.guix-profile/bin/emacs
/run/current-system/profile/bin/emacs
$ ls -l /home/dev_1/.guix-profile/bin/emacs
lrwxrwxrwx 8 root root 64 Jan 1 1970 /home/dev_1/.guix-profile/bin/emacs
-> /gnu/store/6mw831p6pccqwr3k3qanr6pmhcq0qym6-emacs-27.1/bin/emacs
$ ls -l /run/current-system/profile/bin/emacs
lrwxrwxrwx 2 root root 64 Jan 1 1970
/run/current-system/profile/bin/emacs ->
/gnu/store/yy66pbp3h5mw5sv7hrl1778skapszq7k-emacs-27.1/bin/emacs
```
Now $EMACSLOADPATH contains 6 paths with
"$GUIX_PROFILE/share/emacs/site-lisp" in it:
```
$ echo $EMACSLOADPATH
/home/dev_1/.guix-profile/share/emacs/site-lisp:/home/dev_1/.guix-profile/share/emacs/27.1/lisp:/home/dev_1/.guix-profile/share/emacs/site-lisp:/home/dev_1/.guix-profile/share/emacs/27.1/lisp:/run/current-system/profile/share/emacs/site-lisp:/run/current-system/profile/share/emacs/27.1/lisp
```
Before $EMACSLOADPATH contains only 2 paths without
"$GUIX_PROFILE/share/emacs/site-lisp" in it.
I think my first emacs installation should has something break,so
$EMACSLOADPATH isn't correctly set.
Thanks again
Le dim. 21 nov. 2021 à 04:25, Maxim Cournoyer a
écrit :
> Hello,
>
> bbb ee writes:
>
> > ## Description of bug
> > emacs can't load packages installed by guix because missing
> > $GUIX_PROFILE/share/emacs/site-lisp
> > in EMACSLOADPATH
> >
> > $GUIX_PROFILE/share/emacs/site-lisp isn't set in my
> > $GUIX_PROFILE/etc/profile and not in my $EMACSLOADPATH
> >
> > ```
> > $ echo $EMACSLOADPATH
> >
> /run/current-system/profile/share/emacs/site-lisp:/run/current-system/profile/share/emacs/27.1/lisp
> >
> > $ less $GUIX_PROFILE/etc/profile
> > export
> >
> EMACSLOADPATH="${GUIX_PROFILE:-/gnu/store/vq5dzmbx202z9p5hjyxfzcdpyzapxgxg-profile}/share/emacs/site-lisp:${GUIX_PROFILE:-/gnu/store/vq5dzmbx202z9p5hjyxfzcdpyzapxgxg-profile}/share/emacs/27.1/lisp${EMACSLOADPATH:+:}$EMACSLOADPATH"
> >
> > ```
>
> The EMACSLOADPATH environment variable is set when installing Emacs
> itself; have you installed the 'emacs' package in your profile (guix
> install emacs), then sourced your profile again
> (. ~/.guix-profile/etc/profile), or alternatively started a new shell?
>
> This works for me, for example:
>
> --8<---cut here---start->8---
> $ guix shell --container emacs emacs-magit -- emacs --batch --eval \
> '(begin (print (getenv "EMACSLOADPATH") (print (magit-version))'
> Loading
> /gnu/store/hsj3kl0vc3hxiapklg5nj42z5jb4s80p-emacs-magit-3.3.0/share/emacs/site-lisp/magit-3.3.0/magit-autoloads...
> [...]
>
> "/gnu/store/zv9iqvv6jnnvf0cr0c8kan3dcgj8mybj-profile/share/emacs/site-lisp:/gnu/store/ybpddmq7f8ajzydhiqqx6dldgmadqanp-emacs-27.2/share/emacs/27.2/lisp"
>
> "3.3.0"
> --8<---cut here---end--->8---
>
> HTH,
>
> Maxim
>
bug#52002: missing $GUIX_PROFILE/share/emacs/site-lisp in EMACSLOADPATH
## Description of bug
emacs can't load packages installed by guix because missing
$GUIX_PROFILE/share/emacs/site-lisp
in EMACSLOADPATH
$GUIX_PROFILE/share/emacs/site-lisp isn't set in my
$GUIX_PROFILE/etc/profile and not in my $EMACSLOADPATH
```
$ echo $EMACSLOADPATH
/run/current-system/profile/share/emacs/site-lisp:/run/current-system/profile/share/emacs/27.1/lisp
$ less $GUIX_PROFILE/etc/profile
export
EMACSLOADPATH="${GUIX_PROFILE:-/gnu/store/vq5dzmbx202z9p5hjyxfzcdpyzapxgxg-profile}/share/emacs/site-lisp:${GUIX_PROFILE:-/gnu/store/vq5dzmbx202z9p5hjyxfzcdpyzapxgxg-profile}/share/emacs/27.1/lisp${EMACSLOADPATH:+:}$EMACSLOADPATH"
```
## Workaround used
add in init.el
```
(add-to-list 'load-path "/home/dev_1/.guix-profile/share/emacs/site-lisp")
(guix-emacs-autoload-packages)
```
## version
emacs 27.1
