bug#69667: build of sway-1.9-checkout.drv failed
guix home reconfigure fails at sway-1.9. The bottom of the drv file shows this, ``` `source is at 'sway-1.9-checkout' Backtrace: 10 (primitive-load "/gnu/store/5ahfcp5009pgdh17lg5y01w4vhv…") In ice-9/eval.scm: 619:8 9 (_ #(#(# "swa…") #)) In ice-9/boot-9.scm: 142:2 8 (dynamic-wind _ _ #) In system/base/compile.scm: 352:28 7 (compile _ #:from _ #:to _ #:env _ #:optimization-level …) 265:44 6 (_ _ _) 265:44 5 (_ _ _) 265:44 4 (_ _ _) 261:27 3 (_ _ _) In ice-9/boot-9.scm: 2836:4 2 (save-module-excursion #) In language/bytecode/spec.scm: 43:19 1 (_) In unknown file: 0 (delete-file "contrib/grimshot.1") ERROR: In procedure delete-file: In procedure delete-file: No such file or directory /gnu/store/5wqhngwwzaa9b9g1apxr8lawk3g8sxwm-sway-1.9-checkout/assets/Sway_Wallpaper_Blue_1136x640_Portrait.png' -> `sway-1.9-checkout/assets/Sway_Wallpaper_Blue_1136x640_Portrait.png' `/gnu/store/5wqhngwwzaa9b9g1apxr8lawk3g8sxwm-sway-1.9-checkout/assets/Sway_Wallpaper_Blue_768x1024.png' -> `sway-1.9-checkout/assets/Sway_Wallpaper_Blue_768x1024.png' `/gnu/store/5wqhngwwzaa9b9g1apxr8lawk3g8sxwm-sway-1.9-checkout/assets/Sway_Wallpaper_Blue_1920x1080.png' -> `sway-1.9-checkout/assets/Sway_Wallpaper_Blue_1920x1080.png' `/gnu/store/5wqhngwwzaa9b9g1apxr8lawk3g8sxwm-sway-1.9-checkout/assets/Sway_Logo+Text_Ver3.svg' -> `sway-1.9-checkout/assets/Sway_Logo+Text_Ver3.svg' `/gnu/store/5wqhngwwzaa9b9g1apxr8lawk3g8sxwm-sway-1.9-checkout/assets/Sway_Tree.svg' -> `sway-1.9-checkout/assets/Sway_Tree.svg' `/gnu/store/5wqhngwwzaa9b9g1apxr8lawk3g8sxwm-sway-1.9-checkout/assets/Sway_Logo+Text_Ver1_1500x716.png' -> `sway-1.9-checkout/assets/Sway_Logo+Text_Ver1_1500x716.png' `/gnu/store/5wqhngwwzaa9b9g1apxr8lawk3g8sxwm-sway-1.9-checkout/assets/Sway_Logo+Text_Ver4.png' -> `sway-1.9-checkout/assets/Sway_Logo+Text_Ver4.png' ```
bug#69648: [bug#69622] [PATCH] gnu: plasma-desktop: fix build.
Zheng Junjie writes: > * gnu/packages/kde-plasma.scm (plasma-desktop): fix build. > [inputs]: Replace qtwayland with qtwayland-5. Pushed as commit e51c26ef2d, thank you! Also fixes #69648, close both.
bug#69655: WARNING: Use of 'load' in declarative module
Starting a long time ago, maybe a year ago, I begin seeing this warning screen.
The screen appears for a brief moment, after submitting login to wlgreet and
before sway desktop is started. I took a cellphone picture of the screen in
order to copy the message shown,
```
starting service root...
Service root started
Service root running with value #t.
Service root has been started.
WARNING: Use of 'load' in declarative module (#( gl107)#) Add #:declarative?
#f to your define-module invocation
Daemonizing...
Some deprecated features have been used. Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information. Set it to "no" to supress
this message.
Restarting signal handler.
Now running as process 330.
Starting services...
Configuration succesfully loaded from '/gnu/store/hcj[...]x96-shepherd.conf'.
Starting service gpg-agent
Service gpg-agent has been started.
Service gpg-agent started.
Service gpg-agent running with value (("ssh" . #)
("browser" . #) ("extra" . #)
("std" . #)).
Succesfully started 2 services in the background
```
Added GUILE_WARN_DEPRECATED="detailed" to my home config results in the
messages below,
```
starting service root...
Service root started
Service root running with value #t.
Service root has been started.
WARNING: Use of 'load' in declarative module (#( gl107)#) Add #:declarative?
#f to your define-module invocation
GOOPS method 'action' is deprecated in favor of procedure
'perform-service-action'
Daemonizing...
Restarting signal handler.
Now running as process 312.
Starting services...
Configuration succesfully loaded from '/gnu/store/m9q[...]w0f-shepherd.conf'.
Starting service gpg-agent
Service gpg-agent has been started.
Service gpg-agent started.
Service gpg-agent running with value (("ssh" . #)
("browser" . #) ("extra" . #)
("std" . #)).
Succesfully started 2 services in the background
```
Any help or advice is appreciated. Thank you,
Chris
bug#69653: grafts require all outputs (e.g. large debug symbols) to be downloaded to operate
Hi, This has been annoying me for a while; building e.g. a grafted qttools (currently the case on master) will require the whole qtbase:debug output to be downloaded, which even when compressed weighs a whooping 300 MiB. Could it be possible to have some outputs disregarded for the purpose of grafting, e.g. 'debug'? -- Thanks, Maxim
bug#69617: guix go import fails on some version tags
On 2024-03-07 10:18:52 -0800, Ryan Barber wrote:
> In some cases the "guix import go" command fails when attempting to
> checkout the source for a module using a tag which does not exist in
> the repo.
>
> Upon further investigation, I have found guix/import/go.scm will use
> the version string as tag. While this works most of the time, some
> module vendors use a different tagging scheme. For example, the
> azure-sdk-for-go repository contains many modules and the version tags
> are namespaced by module name.
>
> The tag for version v1.3.0 of azure-sdk-for-go/sdk/storage/azblob is
> storage/azblob/v1.3.0.
>
> $ curl -s
> 'https://proxy.golang.org/github.com/!azure/azure-sdk-for-go/sdk/storage/azblob/@v/v1.3.0.info'
> | jq
> {
> "Version": "v1.3.0",
> "Time": "2024-02-12T16:20:44Z",
> "Origin": {
> "VCS": "git",
> "URL": "https://github.com/Azure/azure-sdk-for-go;,
> "Subdir": "sdk/storage/azblob",
> "Ref": "refs/tags/sdk/storage/azblob/v1.3.0",
> "Hash": "d5dfa9296a115cc5094b14198b7114a64a490994"
> }
> }
>
> I have a patch to fix this, but I would like to discuss the approach
> before submitting it. Should I reply to this bug report with the
> patch?
I wonder, even if you manage to import it, will go-build-system be able to build
it? That was what stopped me last time I looked into this, I reached the
conclusion that current go-build-system cannot handle multiple go modules with
overlapping paths.
Out of curiosity, what was your approach to this issue?
>
> Here is the backtrace when attempting to run import on storage/azblob
>
> $ guix import go github.com/Azure/azure-sdk-for-go/sdk/storage/azblob
> Backtrace:
> 14 (primitive-load "/home/rfb/.config/guix/current/bin/guix")
> In guix/ui.scm:
>2324:7 13 (run-guix . _)
> 2287:10 12 (run-guix-command _ . _)
> In guix/scripts/import.scm:
> 80:6 11 (guix-import . _)
> In ice-9/boot-9.scm:
> 1752:10 10 (with-exception-handler _ _ #:unwind? _ # _)
> In guix/scripts/import/go.scm:
>116:29 9 (_)
> In ice-9/exceptions.scm:
>406:15 8 (go-module->guix-package* . _)
> In ice-9/boot-9.scm:
> 1752:10 7 (with-exception-handler _ _ #:unwind? _ # _)
> In guix/import/go.scm:
>532:19 6 (go-module->guix-package "github.com/Azure/azure-sdk-f…" …)
> In guix/git.scm:
> 295:4 5 (update-cached-checkout _ #:ref _ #:recursive? _ # _ # _ …)
>281:19 4 (resolve _)
> In git/reference.scm:
> 60:8 3 (_ _ _)
> In git/bindings.scm:
> 77:2 2 (raise-git-error _)
> In ice-9/boot-9.scm:
> 1685:16 1 (raise-exception _ #:continuable? _)
> 1683:16 0 (raise-exception _ #:continuable? _)
>
> ice-9/boot-9.scm:1683:16: In procedure raise-exception:
> Git error: reference 'refs/tags/v1.3.1' not found
>
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
