Can't change ikiwiki settings

Problem Description
After installing ikiwiki and creating up a wiki, I cannot change wiki settings. I have created a couple of wiki pages and wanted to experiment with different themes.

Steps to Reproduce

  1. Log into ikiwiki using the admin account that created the wiki.
  2. Click the Preferences link on the wiki page.
  3. Click the Setup button on the ikiwiki preferences page.
  4. Change a setting (I unchecked the “Enable Discussion pages?” option and enabled the theme plugin).
  5. Click the Save Setup button at the bottom of the ikiwiki preferences page

Expected Results
The wiki is regenerated with the changes.

Actual results
I get an page with the following message:

...
Use of uninitialized value in string ne at /usr/share/perl5/IkiWiki.pm line 693.
refreshing wiki..
You asked to pull from the remote 'origin', but did not specify
a branch. Because this is not the default configured remote
for your current branch, you must specify a branch on the command line.
'git pull --prune origin' failed:  at /usr/share/perl5/IkiWiki/Plugin/git.pm line 251.
done

Information

  • Debian GNU/Linux 12 (bookworm) and FreedomBox version 23.6.2
  • Physical server AMD E-450 APU
  • apt install freedombox several years ago

I was not able to reproduce this issue with the development container - I installed ikiwiki in the container and created a wiki which worked correctly when I changed the setup.

A sudo git pull on the physical freedombox resulted in:

There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.

git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=origin/<branch> main

So I followed the advice:

sudo git branch --set-upstream-to=origin/main main

and git is now happy. I can now change settings on my wiki.

I noticed that on my physical freedombox the wiki is on git branch main, while in the container the wiki is on git branch master. I’m not sure if that explains the different behavior though.