mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-24 07:30:57 +01:00
Build results in ImageMagick errors #8
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#8
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @joshuaboniface on GitHub (Dec 9, 2018).
@JustAMan wondering if you've hit this:
dotnet publish --configuration Release /var/home/joshua/Projects/Emby/jellyfin/MediaBrowser.sln --output='/var/home/joshua/Projects/Emby/jellyfin/usr/lib/jellyfin/bin'etc.
I suppose the
debian/rulesconfig is missing a step, any thoughts?@joshuaboniface commented on GitHub (Dec 9, 2018):
Oh I needed to initialize and grab the submodules.
@JustAMan commented on GitHub (Dec 9, 2018):
Yes, submodules. Pls clone them to this organization as well, that should be a proper way.
@dcrdev commented on GitHub (Dec 9, 2018):
Actually newer versions of Emby utilise skia and the only reason they package imagemagick directly was to prevent users having differing versions across platforms - imagemagick being particularly prone to abi changes.
Skia would be the way to go - it's available in nuget and would therefore negate the need to include it in this repository at all.
I'll do some work on a new server entry point at some point, that'll solve this.