bug#60694: Acknowledgement (Issue building derivations in 1.4.0)

[Tom Parker-Shemilt]

I hit this while running in a low-CPU Virtualbox setup doing some
Packer work on https://github.com/palfrey/guix-vm. I upped the CPU
specs and got another error

==> virtualbox-iso: Backtrace:
==> virtualbox-iso: In ice-9/eval.scm:
==> virtualbox-iso: 155:9 19 (_ _)
==> virtualbox-iso: 159:9 18 (_
#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(# ?) ?) ?) ?) ?)
?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?))
==> virtualbox-iso: In ice-9/boot-9.scm:
==> virtualbox-iso: 152:2 17 (with-fluid* _ _ _)
==> virtualbox-iso: 152:2 16 (with-fluid* _ _ _)
==> virtualbox-iso: In ./guix/store.scm:
==> virtualbox-iso:   2170:24 15 (run-with-store # #
?)
==> virtualbox-iso:1998:8 14 (_ #)
==> virtualbox-iso: In ./guix/gexp.scm:
==> virtualbox-iso:299:22 13 (_ #)
==> virtualbox-iso:1180:2 12 (_ #)
==> virtualbox-iso:1046:2 11 (_ #)
==> virtualbox-iso: 892:4 10 (_ #)
==> virtualbox-iso: In ./guix/store.scm:
==> virtualbox-iso:   2055:12  9 (_ #)
==> virtualbox-iso:   1407:13  8 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  7 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  6 (map/accumulate-builds
# # ?)
==> virtualbox-iso:1403:5  5 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1419:15  4 (_ # ("/gnu/store/hvjrj0dmfjfh95wr5xn1hgwyw2nyaqlc-subversion?"
?) ?)
==> virtualbox-iso:   1419:15  3 (loop #f)
==> virtualbox-iso:713:11  2 (process-stderr # _)
==> virtualbox-iso: In ./guix/serialization.scm:
==> virtualbox-iso:102:11  1 (read-int #)
==> virtualbox-iso:  80:6  0 (get-bytevector-n* # 8)
==> virtualbox-iso:
==> virtualbox-iso: ./guix/serialization.scm:80:6: In procedure
get-bytevector-n*:
==> virtualbox-iso: ERROR:
==> virtualbox-iso:   1. :
==> virtualbox-iso:   file: #f
==> virtualbox-iso:   port: #
==> virtualbox-iso: guix pull: error: You found a bug: the program
'/gnu/store/lzinbzm0hxvnz11c4cin1ml9ybhrg7r5-compute-guix-derivation'
==> virtualbox-iso: failed to compute the derivation for Guix
(version: "8e2f32cee982d42a79e53fc1e9aa7b8ff0514714"; system:
"x86_64-linux";
==> virtualbox-iso: host version: "1.4.0"; pull-version: 1).
==> virtualbox-iso: Please report the COMPLETE output above by email
to .

On Mon, 9 Jan 2023 at 18:34, GNU bug Tracking System
 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@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 60...@debbugs.gnu.org.
>
> Please do not send mail to help-debb...@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 60694: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60694
> GNU Bug Tracking System
> Contact help-debb...@gnu.org with problems

bug#58813: can't substitute etc/teams.scm command as doc suggests

[Maxim Cournoyer]

Hi Ludovic,

Ludovic Courtès  writes:

> Hi,
>
> Maxim Cournoyer  skribis:
>
>> Simon Tournier  writes:
>>
>>> Hi Ludo,
>>>
>>> On Tue, 03 Jan 2023 at 23:29, Ludovic Courtès  wrote:
>>>
 The manual recommends this (info "(guix) Teams"):

   git send-email --to issue_num...@debbugs.gnu.org $(./etc/teams.scm cc 
 mentors) *.patch

 where:

 --8<---cut here---start->8---
 λ ./etc/teams.scm cc mentors
 --add-header="X-Debbugs-Cc: r...@raghavgururajan.name"
 --add-header="X-Debbugs-Cc: zimon.touto...@gmail.com" …
 --8<---cut here---end--->8---

 I believe this cannot work because the shell will split words on each
 whitespace; IOW, the double quotes above do not have the desired effect.
>>
>>> Well, IIUC, this part is tracked by #58813 [1].
>>>
>>> 1: 
>>
>> Indeed (CC'd).
>>
>> I thought about not using whitespace in the generated output, but I'm
>> not sure if Debbugs or email clients in general would care, plus it's a
>> dirty fix.
>
> Right.
>
> How about just outputting a line like:
>
>   X-Debbugs-Cc: ma...@example.org, l...@example.org
>
> that people would paste in their cover letter?

Yes, that's better.

> How do Linux’s scripts work?

I think the scripts just print stuff at the terminal and expect the user
to copy paste.  Patman can be used to provide automation on top of that.

>> With the recent patman integration merged (though do apply #60576 as a
>> fixup commit), I'm tempted to remove the mentions of git send-email
>> $(etc/teams.scm cc-members ...) and replace that by 'Further automation
>> of git send-email and etc/teams.scm is possible via the patman package'.
>>
>> What do you think?
>
> This is the first time I hear about patman.  :-)
>
> The “Submitting Patches” section mentions ‘git send-email’; I don’t
> think this is about to change, is it?

It wouldn't change; patman would be hinted at briefly with a reference
to its documentation (info '(u-boot) Patman patch manager' from the
u-boot-documentation package) as a nice way to stay organize with
submissions and automate a few things on top of git send-email.

-- 
Thanks,
Maxim

bug#60694: Issue building derivations in 1.4.0

[Tom Parker-Shemilt]

==> virtualbox-iso: Backtrace:
==> virtualbox-iso:   18 (primitive-load
"/gnu/store/lzinbzm0hxvnz11c4cin1ml9ybhrg7r5-compute-guix-derivation")
==> virtualbox-iso: In ice-9/eval.scm:
==> virtualbox-iso: 155:9 17 (_ _)
==> virtualbox-iso: 159:9 16 (_
#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(#(# ?) ?) ?) ?) ?)
?) ?) ?) ?) ?) ?) ?) ?) ?) ?) ?))
==> virtualbox-iso: In ice-9/boot-9.scm:
==> virtualbox-iso: 152:2 15 (with-fluid* _ _ _)
==> virtualbox-iso: 152:2 14 (with-fluid* _ _ _)
==> virtualbox-iso: In ./guix/store.scm:
==> virtualbox-iso:   2170:24 13 (run-with-store # #
?)
==> virtualbox-iso:1998:8 12 (_ #)
==> virtualbox-iso: In ./guix/gexp.scm:
==> virtualbox-iso:299:22 11 (_ #)
==> virtualbox-iso:1180:2 10 (_ #)
==> virtualbox-iso:1046:2  9 (_ #)
==> virtualbox-iso: 892:4  8 (_ #)
==> virtualbox-iso: In ./guix/store.scm:
==> virtualbox-iso:   2055:12  7 (_ #)
==> virtualbox-iso:   1407:13  6 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  5 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  4 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1407:13  3 (map/accumulate-builds
# # ?)
==> virtualbox-iso:1403:5  2 (map/accumulate-builds
# # ?)
==> virtualbox-iso:   1419:15  1 (_ # ("/gnu/store/p23y74y51gj4vml3mjlg9swx0gg4k22s-ruby-2.7.7.d?")
?)
==> virtualbox-iso:   1419:15  0 (loop #f)
==> virtualbox-iso:
==> virtualbox-iso: ./guix/store.scm:1419:15: In procedure loop:
==> virtualbox-iso: ERROR:
==> virtualbox-iso:   1. :
==> virtualbox-iso:   message: "some substitutes for the outputs
of derivation `/gnu/store/p23y74y51gj4vml3mjlg9swx0gg4k22s-ruby-2.7.7.drv'
failed (usually happens due to networking issues); try `--fallback' to
build derivation from source "
==> virtualbox-iso:   status: 1
==> virtualbox-iso: guix pull: error: You found a bug: the program
'/gnu/store/lzinbzm0hxvnz11c4cin1ml9ybhrg7r5-compute-guix-derivation'
==> virtualbox-iso: failed to compute the derivation for Guix
(version: "8e2f32cee982d42a79e53fc1e9aa7b8ff0514714"; system:
"x86_64-linux";
==> virtualbox-iso: host version: "1.4.0"; pull-version: 1).
==> virtualbox-iso: Please report the COMPLETE output above by email
to .

bug#60688: guix: home: environment-variables: Breaking change 73684dc90

[Kabelo Moiloa via Bug reports for GNU Guix]

Before this commit it was possible to build a guix home configuration where 
home-environment-variables-service-type could ungexp any file-like object such 
as a package. The commit 73684dc90 forces it to be a string, which contradicts 
the documentation for guix. 

Concretely, guix home environment test-home.scm worked before that commit where 
test-home.scm is attached to this email.

-- 
 Regards,
Kabelo M'sobomvu Moiloa
(use-modules (guix gexp)
 (gnu home)
 (gnu home services)
 (gnu packages base)
 (gnu services))

(home-environment
 (services
  (list
   (simple-service 'add-environment-variable
   home-environment-variables-service-type
   `(("PACKAGE" . ,(file-append hello "/bin/hello")))

bug#57844:

[Zacchaeus Scheffer]

Oh wow, should have read closer.  That's a shepherd socket, not a syncthing
socket.  (happened across this thread searching syncthing)

Please Disregard,
Zacchae

bug#58813: can't substitute etc/teams.scm command as doc suggests

[Ludovic Courtès]

Hi,

Maxim Cournoyer  skribis:

> Simon Tournier  writes:
>
>> Hi Ludo,
>>
>> On Tue, 03 Jan 2023 at 23:29, Ludovic Courtès  wrote:
>>
>>> The manual recommends this (info "(guix) Teams"):
>>>
>>>   git send-email --to issue_num...@debbugs.gnu.org $(./etc/teams.scm cc 
>>> mentors) *.patch
>>>
>>> where:
>>>
>>> --8<---cut here---start->8---
>>> λ ./etc/teams.scm cc mentors
>>> --add-header="X-Debbugs-Cc: r...@raghavgururajan.name"
>>> --add-header="X-Debbugs-Cc: zimon.touto...@gmail.com" …
>>> --8<---cut here---end--->8---
>>>
>>> I believe this cannot work because the shell will split words on each
>>> whitespace; IOW, the double quotes above do not have the desired effect.
>
>> Well, IIUC, this part is tracked by #58813 [1].
>>
>> 1: 
>
> Indeed (CC'd).
>
> I thought about not using whitespace in the generated output, but I'm
> not sure if Debbugs or email clients in general would care, plus it's a
> dirty fix.

Right.

How about just outputting a line like:

  X-Debbugs-Cc: ma...@example.org, l...@example.org

that people would paste in their cover letter?

How do Linux’s scripts work?

> With the recent patman integration merged (though do apply #60576 as a
> fixup commit), I'm tempted to remove the mentions of git send-email
> $(etc/teams.scm cc-members ...) and replace that by 'Further automation
> of git send-email and etc/teams.scm is possible via the patman package'.
>
> What do you think?

This is the first time I hear about patman.  :-)

The “Submitting Patches” section mentions ‘git send-email’; I don’t
think this is about to change, is it?

Thanks,
Ludo’.

bug#57844: (no subject)

[Zacchaeus Scheffer]

Hi all,

Not sure if it is relevant, but I have often had this problem, and it
has always been from an orphaned syncthing process.  I.e, the user login
session which has my guix home services running in it ends, but the
syncthing process is not terminated.  Then I start a new login, and it
tries to start a NEW syncthing service, and gives this same error.

You can check this (next time syncthing fails to start) with:
ps -e | grep syncthing

Hope this helps,
Zacchae

bug#57919: xscreensaver 6.04 "Authentication failed" error with correct password

[Christine Lemmer-Webber]

Duplicate of #57071, closing.

(And yes, it's unfortunate.  I miss xscreensaver.)

Nathan Dehnel  writes:

> If I attempt to lock the screen, it locks with "xflock" instead of
> xscreensaver. If I run "xscreensaver-demo", I get
>
> "The XScreenSaver daemon doesn't seem to be running on display ":1.0".
> Launch it now?"
>
> If I click "yes", then xscreensaver starts running when the computer
> is locked, but I get "Authentication failed", and I have to switch
> TTYs and killall xscreensaver to get back into my desktop.
> Config:
>   (screen-locker-service xscreensaver "xscreensaver")

bug#48468: substitute server connection timeout

[Ludovic Courtès]

Hi,

Mathieu Othacehe  skribis:

>> Instead of an env. var., maybe add a ‘--debug’ command-line option and
>> parameterize ‘%debug?’ accordingly?
>
> The --debug command-line feels better but it involves a guix-daemon
> modification so I kept the environment variable,

Oh sorry, I was confusing ‘substitute’ and ‘publish’, that makes sense!

Ludo’.

bug#60688: guix: home: environment-variables: Breaking change 73684dc90

[Andrew Tropin]

yhetil mirror is a little behind and I've not received this email thread
yet and thus it's not in my guix-home notmuch search.  A few minutes ago
I saw you forwarded this thread to me and patches look good, but I
already made and pushed similiar changes.  Sorry for inconvenience.

-- 
Best regards,
Andrew Tropin


signature.asc
Description: PGP signature