bug#48240: “guix copy” to host with daemon listening on TCP fails

2021-05-12 Thread Simon Streit
Ludovic Courtès writes: > Hi, > > Simon Streit skribis: > >> Then it was suggested I checkout to commit >> dd14678b9b9843be20e2bbb98ceb30d2433dab82 and force downgrade my new >> system. While doing so, I noticed that guix-daemon would still offload, >> while if I'd type in `guix offload test`,

bug#48240: “guix copy” to host with daemon listening on TCP fails

2021-05-12 Thread Simon Streit
Ludovic Courtès writes: > Fixed in da28efef36af8925bcd9e40a81cbf552cf8c2d02. Let me know if it > works for you! I'll try it later. I missed this mail yesterday. Cheers!

bug#48240: “guix copy” to host with daemon listening on TCP fails

2021-05-12 Thread Simon Streit
Ludovic Courtès writes: > Simon Streit skribis: >> Anyway, back to this old commit offloading works for all users. > > Is the socket file name displayed above correct? Or did you specify > something else in the record? No, nothing that I'm aware about. I haven't made any special changes. >

bug#48240: “guix copy” to host with daemon listening on TCP fails

2021-05-11 Thread Ludovic Courtès
Bone Baboon skribis: > Ludovic Courtès writes: >> Fixed in da28efef36af8925bcd9e40a81cbf552cf8c2d02. Let me know if it >> works for you! > > This commit appears to have fixed a problem with guix copy that I was > having yesterday. I was getting this error "guix copy: error: failed to > connect

bug#48240: “guix copy” to host with daemon listening on TCP fails

2021-05-11 Thread Bone Baboon via Bug reports for GNU Guix
Ludovic Courtès writes: > Fixed in da28efef36af8925bcd9e40a81cbf552cf8c2d02. Let me know if it > works for you! This commit appears to have fixed a problem with guix copy that I was having yesterday. I was getting this error "guix copy: error: failed to connect over SSH to daemon at '', socket /

bug#48240: “guix copy” to host with daemon listening on TCP fails

2021-05-11 Thread Ludovic Courtès
Hi, Simon Streit skribis: > Then it was suggested I checkout to commit > dd14678b9b9843be20e2bbb98ceb30d2433dab82 and force downgrade my new > system. While doing so, I noticed that guix-daemon would still offload, > while if I'd type in `guix offload test`, I'd get a response: > > guix offload

bug#48240: “guix copy” to host with daemon listening on TCP fails

2021-05-11 Thread Ludovic Courtès
Hi, Simon Streit skribis: > Then it was suggested I checkout to commit > dd14678b9b9843be20e2bbb98ceb30d2433dab82 and force downgrade my new > system. While doing so, I noticed that guix-daemon would still offload, > while if I'd type in `guix offload test`, I'd get a response: > > guix offload

bug#48240: “guix copy” to host with daemon listening on TCP fails

2021-05-08 Thread Ludovic Courtès
Hi, Ricardo Wurmus skribis: > There are two hosts running Guix. The target host runs > “guix-daemon” with “--listen=0.0.0.0:”; it does not listen on > a local socket file. Trying to copy store items to the target > host fails with this backtrace: I pushed the four patches as 3270308eeb

bug#48240: “guix copy” to host with daemon listening on TCP fails

2021-05-05 Thread Ricardo Wurmus
There are two hosts running Guix. The target host runs “guix-daemon” with “--listen=0.0.0.0:”; it does not listen on a local socket file. Trying to copy store items to the target host fails with this backtrace: --8<---cut here---start->8--- [me@here:~]