I rebuilt the package, now it require libsuil-0-0 (>= 0.4.2), this should be fine. Just re-download it from the same release. пт, 2 янв. 2026 г., 21:59 AVLinux via Cin <[email protected]>:
Hi Andrey,
Ahh I see, yes DMO Repo often does a lot of epoch tricks to avoid update conflicts with official Deb-multimedia, I haven't used it personally for years so I never even thought about that being the possible cause. Anyway, I'll check back tomorrow and re-test the updated Packages, thanks VERY much for maintaining these Packages!!
Best, Glen ---
On 2026-01-02 13:03, Андрей Спицын via Cin wrote:
Glen, thank you for testing! I'm currently using the deb-multimedia repository, and it's enabled on my Debian 13 builder. I'll remove that repo from the builder and rebuild the package.
Best regards, Andrey
пт, 2 янв. 2026 г. в 18:34, AVLinux via Cin <[email protected]>:
Hello and Happy New Year!
First, thanks for all the hard work on the new Cinelerra release and also for quickly incorporating the new H.264 in MKV and MOV request! I am trying to move from the AppImages to the Einhander github packages and on AV Linux 25 (based on Debian 13 Trixie and MX Linux 25) I have a dependency error for libsuil:
Solving dependencies... Error! Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
Unsatisfied dependencies: cin : Depends: libsuil-0-0 (>= 1:0.10.22) but 0.10.22-1 is to be installed Error: Unable to correct problems, you have held broken packages. Error: The following information from --solver 3.0 may provide additional context: Unable to satisfy dependencies. Reached two conflicting decisions: 1. cin:amd64=1:5.1.20260102 is selected for install 2. cin:amd64 Depends libsuil-0-0 (>= 1:0.10.22) but none of the choices are installable: [no choices]
At a glance it appears to be an epoch naming issue, because the system does have 0.10.22-1 already installed but the package wants "1:0.10.22" which is not in the Debian or MX repos.
Just thought I'd mention this in case others on Debian 13 (and derivates) are seeing the same thing..
Best, Glen
-- _______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
_______________________________________________ Cin mailing list -- [email protected] To unsubscribe send an email to [email protected]
С уважением, к.т.н., доц. каф. ТЛХП, ХД и БТ СПбГЛТУ Андрей Александрович Спицын +79500166982