Commit Graph
7 Commits
Author SHA1 Message Date
nyanmisaka 6484e3bdad Update build scripts and dependencies
Signed-off-by: nyanmisaka <nst799610810@gmail.com>
2026-05-28 10:57:06 +08:00
nyanmisaka 191fa642e3 Update Mesa branch to 25.0
Signed-off-by: nyanmisaka <nst799610810@gmail.com>
2025-04-17 22:34:15 +08:00
nyanmisaka ee1dd5fafb Add support for Ubuntu 24.04 LTS (Noble)
Signed-off-by: nyanmisaka <nst799610810@gmail.com>
2024-03-24 04:01:15 +08:00
nyanmisaka 19bc567b5a Hotfix for Mesa driver build
Signed-off-by: nyanmisaka <nst799610810@gmail.com>
2022-10-29 17:23:10 +08:00
nyanmisaka d9ad5b460d Update dependencies
Signed-off-by: nyanmisaka <nst799610810@gmail.com>
2022-10-26 20:54:30 +08:00
Cody Robibero a29971ff29 Remove Debian Stretch 2022-01-02 09:33:42 -07:00
Joshua Boniface 0966a03a34 Add proper multi-dist build process
Adds the ability to configure and build per-release deb files that
can be used effectively with reprepro to provide compatibility
across distros and multiple architectures.

The package contains a set of static, single-binary ffmpeg and
ffprobe binaries that can be used instead of any system ffmpeg
packages, for whatever reason. ffmpeg 4.0.3 was chosen as the
latest Jellyfin-supported version.

The resulting binary files are located in `/usr/share` rather than
`/usr/bin`, so we don't need to `Conflicts` with system ffmpeg
packages. It does require various shared dependencies, following
as closely as possible (while compatible with all supported
releases) the default configurations, all of which should be
available on all releases and architectures by default (as would
the system ffmpeg).

A Docker-based infrastructure similar to the main Jelyfin package
build infrastructure is included to build the various packages
for the supported releases and architectures. The entrypoint
for users cloning the repo is `build`.

This configuration disables all tests as a number of them fail
arbitrarily for unknown reasons on armhf, but not amd64. This might
not be ideal long-term but provides a temporary solution. Reenabling
tests can be done by removing the `override_dh_auto_test:` line in
the `debian/rules` file.
2019-02-25 22:42:33 -05:00