guix system search doesn't show system services from channels

  • Open
  • quality assurance status badge
Details
2 participants
  • Andrew Tropin
  • zimoun
Owner
unassigned
Submitted by
Andrew Tropin
Severity
normal
A
A
Andrew Tropin wrote on 24 Sep 2021 08:58
(address . bug-guix@gnu.org)
87lf3mqx2f.fsf@trop.in
Declared system service in (gnu services tmp) in my channel, did guix
pull with the apropriate channels configuration.

System service from (gnu services tmp) can be used in my
operating-system record, but not searchable with `guix system search`.

Do anyone know reasons for such behavior? Are there any known good
solutions for that problem?
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEKEGaxlA4dEDH6S/6IgjSCVjB3rAFAmFNdxgACgkQIgjSCVjB
3rApZhAAkop62GANrNn5Azlisv8pM9bfbdENnU5QQ7Ng/XIVp7OxnKJF0k1Jg7m3
LHz2iMlbt61geTHcS3c5tWZe7Yrt/xYB3LwSuydaYFx/92RQsnUOjsFydD0IwKQ6
k37lFmyQCPclCb/m76rWUMNbBCnOZJmsvEsm8qrkw/ymeeVJ51wGx80cJiqFeq/E
P7X/h8M83fBw6Otx/WsTJafObWJtOCZDp6cmoheJhenwFtEfz2UXYGmd8SippOva
0tXO9mZ9pMGChlZQ+XCwvkJ/JFPcaex28Kr4A1IgEpkZ0CTPUvj455lP0IpG2OP0
e4h7iBQkTBJ98tahJDz9qXgrvh+PivLAsUTf6NVxlN4b8BmQMNKaQ4vhuvm6CH+c
Ur44bWdYs8KEgMl22QxEGQFGvZMAdfhIBUJ7eyAKboRR5SD9ZA7y6I7JIwmiF8LV
cgZLDW58XoOqcu6TlNZVOtKvHE7ysteXrxEzfGOSaWi6pb4PBmjIPSejqwOm0Bf/
gtV/g0a0NEqCyrco2cYj5SB9V6bjKWaDemFfLXeu2/CCSC1BHaiYng+9aApgrwZ3
wL58ezrPGwI3p6INc2HrAh3h3THYt21uKpPNoTDjIIAmr5jylKrN2NdNx61k86K4
wzeZRM5kvFGovs4wjEr12Hk0Bono/L2jOE9usoAZBCglZn6ImMo=
=BRb3
-----END PGP SIGNATURE-----

Z
Z
zimoun wrote on 27 Sep 2021 15:27
(name . Andrew Tropin)(address . andrew@trop.in)(address . 50771@debbugs.gnu.org)
CAJ3okZ1ggEQH0QYiFuBcBR9e2_gY65iS=ePiaack+_wHxE+nOg@mail.gmail.com
Hi,

On Fri, 24 Sept 2021 at 08:59, Andrew Tropin <andrew@trop.in> wrote:
Toggle quote (10 lines)
>
> Declared system service in (gnu services tmp) in my channel, did guix
> pull with the apropriate channels configuration.
>
> System service from (gnu services tmp) can be used in my
> operating-system record, but not searchable with `guix system search`.
>
> Do anyone know reasons for such behavior? Are there any known good
> solutions for that problem?

Does it work if, instead of pulling, you run --load-path?

Cheers,
simon
A
A
Andrew Tropin wrote on 28 Sep 2021 12:26
(name . zimoun)(address . zimon.toutoune@gmail.com)(address . 50771@debbugs.gnu.org)
87zgrxf11z.fsf@trop.in
On 2021-09-27 15:27, zimoun wrote:

Toggle quote (18 lines)
> Hi,
>
> On Fri, 24 Sept 2021 at 08:59, Andrew Tropin <andrew@trop.in> wrote:
>>
>> Declared system service in (gnu services tmp) in my channel, did guix
>> pull with the apropriate channels configuration.
>>
>> System service from (gnu services tmp) can be used in my
>> operating-system record, but not searchable with `guix system search`.
>>
>> Do anyone know reasons for such behavior? Are there any known good
>> solutions for that problem?
>
> Does it work if, instead of pulling, you run --load-path?
>
> Cheers,
> simon

`guix system --load-path=~/work/rde search home` doesn't show the
system service I declared :/

I suspect this problem happens due to implementation:
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEKEGaxlA4dEDH6S/6IgjSCVjB3rAFAmFS7egACgkQIgjSCVjB
3rCeTA//dq/TVnk4ho4pv+9G6g2OcaJ/qxndNZ0J2xB0Ch3RVz5gb0Q8niditzPS
eKCc89K7XC+tcEmoDyZX7qFzSpK0AksMTP3KRP+gPNvzcA1nYk6FPhtqCRcE6Vn9
JhttqWwYNcX/iv+tYn0l79V3KYQ11FZTsN0vE5iXLuU1KHTjx8EKpKJk3yuzXB/R
OFRqQV+P4yZj6Ae7qvZeO6tQHlliBgNlf9Qt4MFUacWFy/FJmVu9vvmPju/eVaIg
wU+hpzbp1GPV3C04F0C6Lhj9ANRp78eH+uhIq8as9kYmhrtz+tl9B8UbR8NPKSVA
Q2d5p56KU/sbP7Nhrd9HBRjW+tPhY9xesgHrgv1LlaZO7xSyRBgTkTFSa92Za42y
FFdZjUkwYAluJsdfhti0DNhVpGljXmRIrhQECWUmqYvxRmqBDvdcWqEN6V0LFaGh
xk1ImzIBDz5h536rLkxQdOhPvIu8j2xq+bAFqiIM7FQ9LWhJANPSl4oeS2U46tfe
1061ZuT8hPWnyzfhfDH681yEqr8q5Zgmze9x5Ab05QtroSjgjFTIWO0CusuGYe//
o2iDN7JbREeUKHO/OfhJCpdPNpqo1vwzeON1Gz5bPIjI29QqbLxHrCnYBFM/BNne
Uc24LVkhYwzRnaljMxnH9PhpNBlBr9VMWjPYJN+PPfXVSC77l9A=
=adVX
-----END PGP SIGNATURE-----

?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 50771@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 50771
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch