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

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

Is that the desktop or the server package?

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)

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

1 Like

+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

Welcome! :wave:

I’ve just enabled your account on Gitea.

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

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

This should be fixed in 8d9cf02d3e, please check with the next unstable build (should be ready for deployment in ~45min, also on try).

Hi,

with the current unstable version from https://dl.vikunja.io/vikunja/unstable/vikunja-unstable-amd64.deb (timestamp 03/26/2025 01:03:49 AM +00:00) dpkg returns “‘Version’ field value ‘main’: version number does not start with digit”.

Installing still works with forcing the instalation with dpkg --force-bad-version.

Something still not correct? Version: main :thinking:

# dpkg-deb -I vikunja-unstable-amd64.deb
 neues Debian-Paket, Version 2.0.
 Größe 33377078 Byte: control-Archiv= 755 Byte.
      24 Byte,     1 Zeilen      conffiles
     380 Byte,    11 Zeilen      control
     190 Byte,     3 Zeilen      md5sums
     393 Byte,     9 Zeilen   *  postinst             #!/bin/bash
 Package: vikunja
 Version: main
 Section: default
 Priority: extra
 Architecture: amd64
 License: AGPLv3
 Maintainer: Vikunja Maintainers <maintainers@vikunja.io>
 Installed-Size: 40374
 Depends: systemd
 Homepage: https://vikunja.io
 Description: Vikunja is an open-source todo application, written in Go. It lets you create lists,tasks and share them via teams or directly between users.

This should work now, can you try again?

Doesn’t seem so. @kolaente

>dpkg -I vikunja-unstable-amd64.deb
 new Debian package, version 2.0.
 size 33391576 bytes: control archive=753 bytes.
      24 bytes,     1 lines      conffiles
     380 bytes,    11 lines      control
     190 bytes,     3 lines      md5sums
     393 bytes,     9 lines   *  postinst             #!/bin/bash
 Package: vikunja
 Version: main
 Section: default
 Priority: extra
 Architecture: amd64
 License: AGPLv3
 Maintainer: Vikunja Maintainers <maintainers@vikunja.io>
 Installed-Size: 40390
 Depends: systemd
 Homepage: https://vikunja.io
 Description: Vikunja is an open-source todo application, written in Go. It lets you create lists,tasks and share them via teams or directly between users.
>vikunja version
Vikunja api version main
Built with go1.23.7

(I fored the installation with --force-bad-version)

It seems like you were using an old deb package. The correct one is called vikunja-unstable-x86_64.deb in the download server. I’ve removed the other one.

Can you check again?

Now it seems correct to me. Version is as expected in package and return value.

Looking better now but unstable version is now 0.24.1~974-2a090123 - shouldn’t the version number from the unstable be > the current stable v0.24.6 :thinking:

~# dpkg-deb -I vikunja-unstable-x86_64.deb
 neues Debian-Paket, Version 2.0.
 Größe 34709450 Byte: control-Archiv= 769 Byte.
      24 Byte,     1 Zeilen      conffiles
     395 Byte,    11 Zeilen      control
     190 Byte,     3 Zeilen      md5sums
     393 Byte,     9 Zeilen   *  postinst             #!/bin/bash
 Package: vikunja
 Version: 0.24.1~974-2a090123
 Section: default
 Priority: extra
 Architecture: amd64
 License: AGPLv3
 Maintainer: Vikunja Maintainers <maintainers@vikunja.io>
 Installed-Size: 43090
 Depends: systemd
 Homepage: https://vikunja.io
 Description: Vikunja is an open-source todo application, written in Go. It lets you create lists,tasks and share them via teams or directly between users.

~# dpkg --install vikunja-unstable-x86_64.deb
dpkg: Warnung: Version 0.24.6 des Paketes vikunja wird durch ältere Version 0.24.1~974-2a090123 ersetzt
(Lese Datenbank ... 105300 Dateien und Verzeichnisse sind derzeit installiert.)
Vorbereitung zum Entpacken von vikunja-unstable-x86_64.deb ...
Entpacken von vikunja (0.24.1~974-2a090123) über (0.24.6) ...
vikunja (0.24.1~974-2a090123) wird eingerichtet ...
...

It is, the release versions just contain backported changes and thus have a different version number. The unstable version can be read as “based off 0.24.1, containing 974 commits since then and the commit it was built from is 2a090123”.

ok but this way it’s a downgrade for the system :wink: