github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

Cannot install vikunja without systemd #2055

New Issue
Closed
opened 2026-03-22 13:53:31 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-03-22 13:53:31 -05:00
Owner
Copy Link

Originally created by @mjk-gh on GitHub (Dec 24, 2024).

Description

I downloaded the Debian package for Vikunja and tried to install it, but it would not install, because systemd is missing (and cannot be installed on my system, which uses SysV-init):

# dpkg -i vikunja-0.24.6-amd64.deb
Selecting previously unselected package vikunja.
(Reading database ... 672346 files and directories currently installed.)
Preparing to unpack vikunja-0.24.6-amd64.deb ...
Unpacking vikunja (0.24.6) ...
dpkg: dependency problems prevent configuration of vikunja:
 vikunja depends on systemd; however:
  Package systemd is not installed.

dpkg: error processing package vikunja (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 vikunja
#

Vikunja does get installed and seems to work just fine, it is just that a SysV init script is missing.

I converted the installed Vikunja systemd service file using systemd-to-sysvinit-converter like so:

python converter.py vikunja.service > /etc/init.d/vikunja

... hacked it a little to make vikunja start in the background (I have next to no knowledge about either init system, SysV or Systemd), and finally, created the start and stop links to the SysV init script:

update-rc.d vikunja defaults

Vikunja can be started and stopped using this SysV script (but not be monitored with it, that would need some more tweaking), see attached file (remove .txt extension, github seems to need a file extension for uploaded files).

I cannot get the accompanying Vikunja desktop package to run, though ("Error: Cannot find module 'body-parser'"), and "npm install body-parser" fails with

# npm install body-parser
npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm ERR! errno UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm ERR! request to https://registry.npmjs.org/body-parser failed, reason: unable to get local issuer certificate

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2024-12-24T21_08_15_818Z-debug-0.log

and I am not sure if I am willing to use something like

npm config set strict-ssl false

But maybe this bug report helps other people with SysV-init based Linux installation.

Vikunja Version

0.24.6

Browser and version

No response

Can you reproduce the bug on the Vikunja demo site?

Please select

Screenshots

No response

Originally created by @mjk-gh on GitHub (Dec 24, 2024). ### Description I downloaded the [Debian](https://dl.vikunja.io/vikunja/0.24.6/vikunja-0.24.6-amd64.deb) package for Vikunja and tried to install it, but it would not install, because systemd is missing (and cannot be installed on my system, which uses SysV-init): ``` # dpkg -i vikunja-0.24.6-amd64.deb Selecting previously unselected package vikunja. (Reading database ... 672346 files and directories currently installed.) Preparing to unpack vikunja-0.24.6-amd64.deb ... Unpacking vikunja (0.24.6) ... dpkg: dependency problems prevent configuration of vikunja: vikunja depends on systemd; however: Package systemd is not installed. dpkg: error processing package vikunja (--install): dependency problems - leaving unconfigured Errors were encountered while processing: vikunja # ``` Vikunja _does_ get installed and seems to work just fine, it is just that a SysV init script is missing. I converted the installed Vikunja systemd service file using [systemd-to-sysvinit-converter](https://github.com/akhilvij/systemd-to-sysvinit-converter) like so: ``` python converter.py vikunja.service > /etc/init.d/vikunja ``` ... hacked it a little to make vikunja start in the background (I have next to no knowledge about either init system, SysV or Systemd), and finally, created the start and stop links to the SysV init script: ``` update-rc.d vikunja defaults ``` Vikunja can be started and stopped using this SysV script (but not be monitored with it, that would need some more tweaking), see [attached file](https://github.com/user-attachments/files/18246785/vikunja.txt) (remove .txt extension, github seems to need a file extension for uploaded files). I cannot get the accompanying Vikunja desktop package to run, though ("Error: Cannot find module 'body-parser'"), and "npm install body-parser" fails with ``` # npm install body-parser npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY npm ERR! errno UNABLE_TO_GET_ISSUER_CERT_LOCALLY npm ERR! request to https://registry.npmjs.org/body-parser failed, reason: unable to get local issuer certificate npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2024-12-24T21_08_15_818Z-debug-0.log ``` and I am not sure if I am willing to use something like ``` npm config set strict-ssl false ``` But maybe this bug report helps other people with SysV-init based Linux installation. ### Vikunja Version 0.24.6 ### Browser and version _No response_ ### Can you reproduce the bug on the Vikunja demo site? Please select ### Screenshots _No response_
GiteaMirror commented 2026-03-22 13:53:31 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 28, 2024):

It's unlikely that we'll officially support other init systems than systemd on debian, simply because it is the standard and supporting multiple different ones in one package isn't exactly easy. You can always install Vikunja manually if that standard doesn't fit your use-case.

I cannot get the accompanying Vikunja desktop package to run, though ("Error: Cannot find module 'body-parser'"), and "npm install body-parser" fails with

This sounds like your certificate store is broken. Does it work with a release desktop package?

@kolaente commented on GitHub (Dec 28, 2024): It's unlikely that we'll officially support other init systems than systemd on debian, simply because it is the standard and supporting multiple different ones in one package isn't exactly easy. You can always install Vikunja manually if that standard doesn't fit your use-case. > I cannot get the accompanying Vikunja desktop package to run, though ("Error: Cannot find module 'body-parser'"), and "npm install body-parser" fails with This sounds like your certificate store is broken. Does it work with a [release desktop package](https://dl.vikunja.io/desktop)?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2055
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?