[Debian] Going from stable to unstable not possible (version number does not start with digit)

Support
1

I just wanted to test the unstable version (installed version now ist v.0.24.6) on my debian test system.

But simply installing the unstable deb package isn’t really possible:

# dpkg -i vikunja-unstable-amd64.deb
dpkg: error processing archive vikunja-unstable-amd64.deb (--install):
 parsing file '/var/lib/dpkg/tmp.ci/control' near line 2 package 'vikunja':
 'Version' field value 'unstable': version number does not start with digit
Errors were encountered while processing:
 vikunja-unstable-amd64.deb
2

Is that the desktop or the server package?

3

https://dl.vikunja.io/vikunja/unstable/vikunja-unstable-amd64.deb

(running https://dl.vikunja.io/vikunja/0.24.6/vikunja-0.24.6-amd64.deb at the moment)

4

Mhh that looks like a bug. I’ll take a look.

1 Like
5

+1
worked around with:

ar x vikunja-unstable-amd64.deb
tar xvf data.tar.gz
mv opt/vikunja/vikunja /opt/vikunja
systemctl restart vikunja

to test LDAP.

My Gitea account is rob but is locked.

1 Like
6

Welcome! :wave:

I’ve just enabled your account on Gitea.

7

So I think the version for the unstable build shouldn’t only be unstable but {upcoming_version}~pre{prerelease_version} - so right now e.g. 0.25~pre1-1, 0.25~pre1-2, …

or using the nightly versioning {upcoming_version}~git{date}.{hash}-{revision} it could be e.g. 0.25~git20250217.67bcdb-1

Syntax:
upcoming_version: The upcoming release version
date: Timestamp in YYYYMMDD format.
hash: 7 characters of git commit hash used for the build (informational purpose).
revision: An internal revision number for that nightly build.

see Versioning - Debian Wiki

8

That’s what it should look like (if you run vikunja version on an unstable build, you should see that) - it’s just that the build process seems to mangle the metadata on this.

1 Like