ikiwiki installation problem?

  • Open
  • quality assurance status badge
Details
2 participants
  • Felicity L.
  • Simon Tournier
Owner
unassigned
Submitted by
Felicity L.
Severity
normal
F
F
Felicity L. wrote on 3 Apr 2023 21:22
(address . bug-guix@gnu.org)
614f859b-6b44-42e9-9d6d-20e56ef28184@app.fastmail.com
Hi Guix Team,

First off thank you for all your work.

So the issue is that when you install "ikiwiki", and then try to follow the guide and run "ikiwiki --setup ...path" you get an error saying ".../.ikiwiki-makerepo-real: line 32: perl: command not found"

I think that the install instructions for arent addint perl to the path right for some reason. Indeed "which perl" cant find perl. I did "guix edit ikiwiki", and it *looks* like there is something about perl and the path in the install phase. Unfortunately Im still too new at this and cant quite parse why it isnt working.

Hopefully one day Ill know enough that I could fix it myself. In the meantime, thank you again for your work.

Best wishes,
Felicity

- Sent from my iPhone
Attachment: file
S
S
Simon Tournier wrote on 16 May 2023 15:33
86wn185rl2.fsf@gmail.com
Hi,

Thanks for your report. And sorry for the late reply.

On Mon, 03 Apr 2023 at 14:22, "Felicity L." <felicity@nekomorphism.com> wrote:

Toggle quote (4 lines)
> So the issue is that when you install "ikiwiki", and then try to
> follow the guide and run "ikiwiki --setup ...path" you get an error
> saying ".../.ikiwiki-makerepo-real: line 32: perl: command not found"

Well, currently ikiwiki is broken because its dependency
python-zope-extensions is broken. Unexpected collateral follow-up of
the recent core-updates merge, probably.

That’s said, propagated-inputs would fix the issue. And that’s probably
the easiest and more straightforward considering all the already long
list of perl-* packages.

Do you want to give a try for fixing this package?


Cheers,
simon
?
Your comment

Commenting via the web interface is currently disabled.

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

To respond to this issue using the mumi CLI, first switch to it
mumi current 62659
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