Mubelotix@jlai.lu to Selfhosted@lemmy.worldEnglish · 2 days agoJellyfin critical security update - This is not a jokegithub.comexternal-linkmessage-square235fedilinkarrow-up1663arrow-down17 cross-posted to: piracy@lemmy.dbzer0.comjellyfin@lemmy.mljellyfin@lemmy.ml
arrow-up1656arrow-down1external-linkJellyfin critical security update - This is not a jokegithub.comMubelotix@jlai.lu to Selfhosted@lemmy.worldEnglish · 2 days agomessage-square235fedilink cross-posted to: piracy@lemmy.dbzer0.comjellyfin@lemmy.mljellyfin@lemmy.ml
minus-squareShortN0te@lemmy.mllinkfedilinkEnglisharrow-up26·1 day ago Is it standard practice to release the security updates on GitHub? Yes. And then the maintainers of the package on the package repository you use will release the patch there. Completely standard operation. I recommend younto read up on package repositories on Linux and package maintainers etc.
Yes.
And then the maintainers of the package on the package repository you use will release the patch there. Completely standard operation.
I recommend younto read up on package repositories on Linux and package maintainers etc.