[PROPOSAL] create Debian trixie package #802

Closed
opened 2026-01-29 16:53:45 +00:00 by claunia · 2 comments
Owner

Originally created by @MatzFan on GitHub (May 22, 2024).

The latest Debian package available is for bullseye. Trixie is now in testing and a trixie package for ccextractor would be great. Bookworm users, like myself, could then use it via the bookworm backports repo.

CCExtractor version: 0.94

In raising this issue, I confirm the following:

  • [y ] I have read and understood the contributors guide.
  • [ y] I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
  • [ y] I have checked that the issue I'm posting isn't already reported.
  • [ y] I have checked that the issue I'm porting isn't already solved and no duplicates exist in closed issues and in opened issues
  • [ y] I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.
  • [ y] I have used the latest available version of CCExtractor to verify this issue exists.
  • [ y] I have ticked all the boxes in this section and to prove it I'm deleting the section completely to remove boilerplate text.

Necessary information

  • Is this a regression (i.e. did it work before)? No
  • What platform did you use? Linux Debian bookworm
  • What were the used arguments? N/A
Originally created by @MatzFan on GitHub (May 22, 2024). The latest Debian package available is for [bullseye](https://packages.debian.org/bullseye/ccextractor). Trixie is now in testing and a trixie package for ccextractor would be great. Bookworm users, like myself, could then use it via the bookworm backports repo. CCExtractor version: 0.94 # In raising this issue, I confirm the following: - [y ] I have read and understood the [contributors guide](https://github.com/CCExtractor/ccextractor/blob/master/.github/CONTRIBUTING.md). - [ y] I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present. - [ y] I have checked that the issue I'm posting isn't already reported. - [ y] I have checked that the issue I'm porting isn't already solved and no duplicates exist in [closed issues](https://github.com/CCExtractor/ccextractor/issues?q=is%3Aissue+is%3Aclosed) and in [opened issues](https://github.com/CCExtractor/ccextractor/issues) - [ y] I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion. - [ y] I have used the latest available version of CCExtractor to verify this issue exists. - [ y] I have ticked all the boxes in this section and to prove it I'm deleting the section completely to remove boilerplate text. # Necessary information - Is this a regression (i.e. did it work before)? No - What platform did you use? Linux Debian bookworm - What were the used arguments? N/A
Author
Owner

@cfsmp3 commented on GitHub (Dec 21, 2025):

I'm looking into this, the problem is that Trixie comes with an older version of Rust (1.85) than then one we need (1.87), and they dropped libGPAC, which we use for MP4.

I think you would be better off by using the Docker version. Take a look at docker/README.md

Anyway we're preparing debian packaging so that Debian mantainers can take over eventually, once these issues are solved (if ever; I think they dropped libGPAC for vulnerability reasons which is reasonable).

@cfsmp3 commented on GitHub (Dec 21, 2025): I'm looking into this, the problem is that Trixie comes with an older version of Rust (1.85) than then one we need (1.87), and they dropped libGPAC, which we use for MP4. I think you would be better off by using the Docker version. Take a look at docker/README.md Anyway we're preparing debian packaging so that Debian mantainers can take over eventually, once these issues are solved (if ever; I think they dropped libGPAC for vulnerability reasons which is reasonable).
Author
Owner

@x15sr71 commented on GitHub (Jan 6, 2026):

Thanks for the context.

I’ve spent some time looking into this from the upstream/build side. From what I can see, GPAC is only used for MP4/ISO-BMFF demuxing, so making it optional at build time looks like a reasonable way to keep CCExtractor buildable on Debian (where GPAC is no longer available), with the understanding that MP4 support would be disabled in that configuration.

In parallel, I’m also reviewing the Rust MSRV requirement to see whether it can be relaxed or pinned in a distro-friendly way for Trixie.

I’ll follow up with focused PRs for these pieces (e.g. optional GPAC / build-time cleanup) rather than a full Debian package, so downstream packaging can be unblocked once the constraints are clearer. Happy to adjust direction if there’s a preferred approach.

@x15sr71 commented on GitHub (Jan 6, 2026): Thanks for the context. I’ve spent some time looking into this from the upstream/build side. From what I can see, GPAC is only used for MP4/ISO-BMFF demuxing, so making it optional at build time looks like a reasonable way to keep CCExtractor buildable on Debian (where GPAC is no longer available), with the understanding that MP4 support would be disabled in that configuration. In parallel, I’m also reviewing the Rust MSRV requirement to see whether it can be relaxed or pinned in a distro-friendly way for Trixie. I’ll follow up with focused PRs for these pieces (e.g. optional GPAC / build-time cleanup) rather than a full Debian package, so downstream packaging can be unblocked once the constraints are clearer. Happy to adjust direction if there’s a preferred approach.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ccextractor#802