bug#68273: 'guix refresh asio' crashes with a match-error

2024-01-05 Thread Maxim Cournoyer
Hello,

--8<---cut here---start->8---
$ guix refresh asio

Backtrace:
In ice-9/boot-9.scm:
  1752:10 16 (with-exception-handler _ _ #:unwind? _ # _)
In unknown file:
  15 (apply-smob/0 #)
In ice-9/boot-9.scm:
724:2 14 (call-with-prompt _ _ #)
In ice-9/eval.scm:
619:8 13 (_ #(#(#)))
In guix/ui.scm:
   2324:7 12 (run-guix . _)
  2287:10 11 (run-guix-command _ . _)
In ice-9/boot-9.scm:
  1752:10 10 (with-exception-handler _ _ #:unwind? _ # _)
  1752:10  9 (with-exception-handler _ _ #:unwind? _ # _)
In guix/store.scm:
   661:37  8 (thunk)
In guix/monads.scm:
576:2  7 (run-with-store # …)
In guix/scripts/refresh.scm:
   657:14  6 (_ _)
In srfi/srfi-1.scm:
634:9  5 (for-each # …)
In guix/scripts/refresh.scm:
   402:10  4 (check-for-package-update #< package: # …)
In srfi/srfi-1.scm:
   858:15  3 (any1 # …)
In guix/gnu-maintenance.scm:
   882:13  2 (latest-sourceforge-release _ #:version _)
In ice-9/boot-9.scm:
  1685:16  1 (raise-exception _ #:continuable? _)
  1685:16  0 (raise-exception _ #:continuable? _)

ice-9/boot-9.scm:1685:16: In procedure raise-exception:
Throw to key `match-error' with args `("match" "no matching pattern" ())'.
--8<---cut here---end--->8---

This case should be handled and do nothing, rather than crash.

-- 
Thanks,
Maxim





bug#68270: libstdc++-boot0.x86_64-linux on core-updates is broken

2024-01-05 Thread Maxim Cournoyer
Hello,

cuir...@gnu.org (Cuirass) writes:

> The build libstdc++-boot0.x86_64-linux for specification 
> core-updates is broken. You can find the detailed information about 
> this build  href="https://ci.guix.gnu.org/build/3012286/details;>here.
>
> https://ci.guix.gnu.org/build/3012286/details

It now fails like:

--8<---cut here---start->8---
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1365:46:
 error: there are no arguments to '__is_trivially_constructible' that depend on 
a template parameter, so a declaration of '__is_trivially_constructible' must 
be available [-fpermissive]
__is_trivially_constructible(_Tp, _Args...)>>
  ^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1365:46:
 error: template argument 2 is invalid
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1365:47:
 error: template argument 2 is invalid
__is_trivially_constructible(_Tp, _Args...)>>
   ^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1409:48:
 error: there are no arguments to '__is_trivially_constructible' that depend on 
a template parameter, so a declaration of '__is_trivially_constructible' must 
be available [-fpermissive]
__is_trivially_constructible(_Tp, const _Tp&)>>
^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1409:48:
 error: template argument 2 is invalid
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1409:49:
 error: template argument 2 is invalid
__is_trivially_constructible(_Tp, const _Tp&)>>
 ^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1417:43:
 error: there are no arguments to '__is_trivially_constructible' that depend on 
a template parameter, so a declaration of '__is_trivially_constructible' must 
be available [-fpermissive]
__is_trivially_constructible(_Tp, _Tp&&)>>
   ^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1417:43:
 error: template argument 2 is invalid
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1417:44:
 error: template argument 2 is invalid
__is_trivially_constructible(_Tp, _Tp&&)>>
^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1425:38:
 error: there are no arguments to '__is_trivially_assignable' that depend on a 
template parameter, so a declaration of '__is_trivially_assignable' must be 
available [-fpermissive]
__is_trivially_assignable(_Tp, _Up)>>
  ^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1425:38:
 error: template argument 2 is invalid
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1425:39:
 error: template argument 2 is invalid
__is_trivially_assignable(_Tp, _Up)>>
   ^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1433:46:
 error: there are no arguments to '__is_trivially_assignable' that depend on a 
template parameter, so a declaration of '__is_trivially_assignable' must be 
available [-fpermissive]
__is_trivially_assignable(_Tp&, const _Tp&)>>
  ^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1433:46:
 error: template argument 2 is invalid
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1433:47:
 error: template argument 2 is invalid
__is_trivially_assignable(_Tp&, const _Tp&)>>
   ^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1441:41:
 error: there are no arguments to '__is_trivially_assignable' that depend on a 
template parameter, so a declaration of '__is_trivially_assignable' must be 
available [-fpermissive]
__is_trivially_assignable(_Tp&, _Tp&&)>>
 ^
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1441:41:
 error: template argument 2 is invalid
/tmp/guix-build-libstdc++-boot0-7.5.0.drv-0/gcc-7.5.0/build/include/type_traits:1441:42:
 error: template argument 2 is invalid
__is_trivially_assignable(_Tp&, _Tp&&)>>
  ^
make[2]: *** [Makefile:876: eh_aux_runtime.lo] Error 1
--8<---cut here---end--->8---

Cuirass says it was caused by one of these:
https://git.savannah.gnu.org/cgit/guix.git/log/?qt=range=62e67aa7994f40c438ef5a528675e85699d7af76..eff2e206881511d04accae1715366e17bf4c2346


bug#63002: Ubuntu 22.04 + GNU Guix, guile-gnutls-3.7.11: dependencies couldn't be built

2024-01-05 Thread Maxim Cournoyer
Hi,

Josselin Poiret  writes:

> Hi Artyom, 
>
> "Artyom V. Poptsov"  writes:
>
>> Initialized empty Git repository in 
>> /gnu/store/dpbxqzqmbhfy7jc2a9dyfi28fdvi04sd-guile-gnutls-3.7.11-checkout/.git/
>> fatal: unable to access 'https://gitlab.com/gnutls/guile/': The requested 
>> URL returned error: 403
>> Failed to do a shallow fetch; retrying a full fetch...
>> fatal: unable to access 'https://gitlab.com/gnutls/guile/': The requested 
>> URL returned error: 403
>> git-fetch: 'git fetch origin' failed with exit code 128
>
> It rather seems like you're just getting a 403 from gitlab, not that
> you can't validate the TLS certificate.  Can you access that url from a
> browser?  Are you using a proxy, but the Guix daemon is somehow not
> using it?

Closing, with the assumption that this was a transient error outside of
the control of Guix.

-- 
Thanks,
Maxim





bug#63077: [PATCH] gnu: gnutls: skip examples on mingw.

2024-01-05 Thread Maxim Cournoyer
Hi Vivien,

Vivien Kraus  writes:

> * gnu/packages/tls.scm (gnutls): Skip the doc/examples subdir on mingw,
> because the gnulib modules are not correct.
> ---
>  gnu/packages/tls.scm | 9 +
>  1 file changed, 9 insertions(+)
>
> diff --git a/gnu/packages/tls.scm b/gnu/packages/tls.scm
> index 6d7cff41b0..9e16b04702 100644
> --- a/gnu/packages/tls.scm
> +++ b/gnu/packages/tls.scm
> @@ -253,6 +253,15 @@ (define-public gnutls
> (substitute* "tests/fastopen.sh"
>   (("^unset RETCODE")
>"exit 77\n"   ;skip
> +   #$@(if (target-mingw?)
> +  #~((add-after 'unpack 'skip-doc-examples
> +   ;; The examples in doc do not link to correct
> +   ;; gnulib modules.
> +   (lambda _
> + (substitute* "doc/Makefile.in"
> +   (("SUBDIRS = examples")
> +"SUBDIRS =")
> +  #~())

Did you report it upstream?  Perhaps they'd know how to properly fix it.

-- 
Thanks,
Maxim





bug#64653: ‘static-networking’ fails to start

2024-01-05 Thread Ludovic Courtès
Hi!

Ludovic Courtès  skribis:

> Evaluating user expression (catch #t (lambda () (load "/gnu/store/64?")) # ?).
> starting 
> '/gnu/store/gn8q7p790a9zdnlciyp1vlncpin366r0-hurd-v0.9.git20230216/hurd/pfinet
>  "--ipv6" "/servers/socket/26" "--interface" "/dev/eth0" "--address" 
> "10.0.2.15" "--netmask" "255.255.255.0" "--gateway" "10.0.2.2"'
> In ice-9/boot-9.scm:
> 142:2  7 (dynamic-wind # ?)
> In shepherd/support.scm:
>486:15  6 (_ #)
> In ice-9/read.scm:
>859:19  5 (read _)
> In unknown file:
>4 (port-filename #)
> In ice-9/boot-9.scm:
>   1685:16  3 (raise-exception _ #:continuable? _)
>   1780:13  2 (_ #< components: (#)
> In ice-9/eval.scm:
> 159:9  1 (_ #(#(#) (# "port-fil?" ?)))
> In unknown file:
>0 (make-stack #t)
> #t
>
> So it’s indeed ‘read’ as called from ‘primitive-load*’ that stumbles
> upon a closed port.

Good news: this is fixed by 4e431fda5f2ec76b6d6a271be7c30b1324431329!
Silly me had introduced a ‘dynamic-wind’ there.

(The funny thing with extensible systems like the Shepherd is that the
problem can be anywhere.  :-))

Ludo’.





bug#53258: Python unable to find modules within a Singularity container created with guix pack

2024-01-05 Thread Konrad Hinsen
Konrad Hinsen  writes:

> Patch at https://issues.guix.gnu.org/68241

If you want to test it without rebuilding tons of packages, here is a
version that grafts a patched Python onto the existing ones (as substitutes):

https://codeberg.org/khinsen/guix/src/branch/graft-fix-python-sitecustomize

Cheers,
  Konrad





bug#68264: awscli@2.2.0 downloads and runs a docker container from a large american corporation

2024-01-05 Thread Collin J. Doering
One thing I deeply appreciate about Gnu Guix is the fact that I have assurance 
that I have installed and am using software that respects my fundamental 
software freedoms. My understanding based on Guix's packaging guidelines 
(https://guix.gnu.org/manual/en/html_node/Packaging-Guidelines.html) is that a 
package should include all necessary software, libraries and resources 
necessary for the program to function; either directly or via dependencies. 
However, it appears that awscli@2.2.0 (and all former versions of the v2 
variant of awscli) download a docker image and run it. This is evident by the 
following, where guix shell is used to run awscli@2.2.0 in a container, but 
docker and its daemon are not present.

--8<---cut here---start->8---
➜ guix shell -C awscli@2.2.0 -- awsv2 --version
2.2.0
AWS CLI v2 command: docker run -i --rm -v /home/collin/.aws:/root/.aws -v 
/home/collin:/aws amazon/aws-cli
14:45:09 - awscliv2 - ERROR - Executable not found: docker
--8<---cut here---end--->8---

I propose awscli@2.2.0 be removed immediately from guix.

Kind regards

PS: I have a packaged version of awscliv2 (2.15.6) available 
https://git.rekahsoft.ca/rekahsoft/rekahsoft-guix/src/branch/master/rekahsoft-gnu/packages/python-xyz.scm#L244-L329

It is still in need of some cleanup, and awscli is in an odd place (given the 
dependencies they vendor and fork), but it does work, and it depends on 
sources. This also follows closely to what nix does (see 
https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/admin/awscli2/default.nix).

-- 
Collin J. Doering

http://rekahsoft.ca
http://blog.rekahsoft.ca
http://git.rekahsoft.ca


signature.asc
Description: PGP signature


bug#68243: alacritty segmentation fault

2024-01-05 Thread Efraim Flashner
On Thu, Jan 04, 2024 at 03:32:55PM +, Steven Roose wrote:
> I've been using alacritty as my default terminal for about a year without
> much issues. I'm currently on v0.12.3 of alacritty and use it with i3 and
> Xorg. A month or two ago I noticed that upgrading GuixSD broke alacritty.
> Since it's my main terminal and I didn't have any other terminals installed,
> I was forced to rollback my system through GRUB because I couldn't literally
> not even open a terminal to investigate or roll-back by CLI. I was trying
> another system upgrade now and noticed the issue is still not fixed. When
> running alacritty from an already-open alacritty only shows me "segmentation
> fault". The working and broken version is both 0.12.3, so I think it might
> not be an alacritty issue but more a linking/build issue. I'm basically
> stuck on a months-old Guix until this is fixed.
> 
> If there is any way I can be of use by providing debug/log files of some
> kind, please let me know.

Looking at 'alacritty --help' it looks like you can try adding -v (up to
3) to get a more verbose output so hopefully we get more of an error
message.

Which generation are you on that is working for you? Which one do you
know is segfaulting? I'd like to try to narrow it down.

-- 
Efraim Flashner  רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted


signature.asc
Description: PGP signature