This is the online depot for Lumiera Debian packages,
usable for automated install and upgrade via apt-get
-
browse the package pool
-
view our package list
![]() |
as of 3/2025, packages have been unmaintained for a long time and most distributions are obsolete; however, š” we currently upgrade to Debian/Trixie as reference system, including a new preview release and refurbish the packages and the DEB depot |
![]() |
Ichthyo’s GPG key for package signing has been upgraded A1DE94B2 (obsolete) → 62382557 |
supported distributions
While currently (planned) the reference for building Lumiera is Debian/Trixie, it is possible to build Debian / Ubuntu / Mint packages for several distributions, based on the same Debian source package. At some point in the future we plan to run an automated package builder; yet right now (3/2025) packaging is a manual process and just done on occasion, to validate the release process — and thus the list of binary distributions is rather limited.
-
Debian/Trixie (testing) : x86_64 (š in work)
-
Ubuntu/Noble (24.04 LTS) : x86_64 (ā planned)
-
Debian/Bookworm (stable) : x86_64 (other packages)
-
Debian/Bullseye (oldstable) : x86_64 (other packages)
![]() |
starting with Lumiera 0.pre.04 we require at least GCC-14 Thus on older distributions, you may need to install a more recent compiler and standard library version from the ppa:ubuntu-toolchain-r/test
(→ see instructions here…) |
release-level components
The Debian archives provide the components main
, contrib
, non-free
while Ubuntu has universe
and multiverse
— in a similar vein, we maintain several release-level components
-
experimental: very rough edged, preliminary bundles
-
planned as of 3/25 — development: development snapshots
-
planned as of 3/25 — release: stable releases for end users
Apt configuration
In order to use the Lumiera Debian-Depot for automated installation via apt-get, you need to
configure your /etc/apt to tell the package manager to consult Lumiera.org for new
packages.
Place a suitable lumiera.sources
file into /etc/apt/sources.lst.d directly and the corresponding GPG-Key
into /etc/apt/keyrings — or use your favourite graphical package management front-end, e.g. synaptic.
(In synaptic, you add this configuration as a new »package source«).
For any of these package manager and installation tasks, you need root (sysadmin) permissions.
![]() |
All contemporary Debian based distributions use »secure Apt«.
It is mandatory to download Ichthyo’s signing key, place it into a
suitable location and refer to it with the Signed-by: field. And,
before doing so, you might want to check at least the key fingerprint
and look at the further address information to see if it’s plausible. |
![]() |
by adding a repository to your package manager configuration you trust the people managing this repository to act reasonable and with common sense. Code from that source will be installed and executed on your system, and the package istelf may contain installation scripts invoked with root permissions. |
To place that into perspective: in a similar way, you also trust the manufacturer of your car, the bank managing your account or your phone and internet provider. With OpenSource and Free Software you get the additional option and benefit that you can look into the details how software is constructed, learn about the reasoning behind the decisions, and get into contact with the people involved (and possibly even get involved yourself…).
The configuration for Apt package source has the following format
Types: deb deb-src
URIs: https://lumiera.org/debian/
Suites: trixie
Components: tool experimental
Signed-By: /etc/apt/keyrings/lumiera-archive-keyring.gpg
The settings should be adjusted accordingly
-
the
Suites:
field defines the distribution to use -
Lumiera is published in the component (section)
experimental
GPG signing key
Modern Debian based systems rely on secure Apt — which refuses to install a package
unless the GPG signature can be verified. The Lumiera packages are signed by Ichthyo’s
GPG key (Key-ID 62382557
Fingerprint 11FD F5D2 DBD7 BBD7 F4D9 D9C4 2CF2 5392 6238 2557
),
which can be retrieved from the usual keyservers (e.g.
here or
here).
Finally, after fetching this public key, you need to store it in binary format at a suitable
location (typically /etc/apt/keyrings) and refer to that location directly from the
source configuration lumiera.sources
gpg --keyserver keyserver.ubuntu.com --recv 62382557
gpg --export 62382557 > lumiera-archive-keyring.gpg
building the source package instead
In case there is no suitable binary package, you’re better off compiling from source, as this yields an executable tailored to your specific system. On Debian/Mint/Ubuntu systems, compiling from Debian source packages is easy and convenient: After adding one of the deb-src lines listed in the table above (pick the one closest to your system), just run:
sudo apt-get build-dep nobug
apt-get source --compile nobug
sudo dpkg -i nobug-dev*deb libnobug*deb
sudo apt-get build-dep libgdlmm-3-dev
apt-get source --compile libgdlmm-3-dev
sudo dpkg -i libgdlmm-3*deb
sudo apt-get build-dep lumiera
apt-get source --compile lumiera
sudo dpkg -i lumiera*deb
→ more on building via Debian source package
Installing
-
For installing precompiled binary packages:
-
add the package source (see above)
-
sudo apt-get update
-
check the configuration:
apt-cache policy lumiera
(version might be different in your case)
lumiera: Candidate: 0.pre.01-3 Version table: *** 0.pre.01-3 0 500 http://lumiera.org buster/experimental Packages
-
install it:
sudo apt-get install lumiera
-
-
If installing a debian package built locally from a debian source package…
after successfully building, you’ll find a
*.deb
package (version and architecture might be different, depending on your situation). If you haven’t already done so, please install these packages onto your system:sudo dpkg -i lumiera_0.pre.01-3_amd64.deb libnobug2_201008.1-2_amd64.deb
After installing successfully, you might want to clean up the build directory.
Maintainer documentation
This Debian-Depot is part of the Lumiera build infrastructure.
It is managed automatically, based on the reprepro tool by Bernhard Link
→ more informations for developers and maintainers