On Mon, 1/4/16, Irrwahn <irrwahn@???> wrote:

Subject: Re: [DNG] Question about the merged repos
To: dng@???
Date: Monday, January 4, 2016, 7:31 AM

On Sun, 3 Jan 2016 17:52:48 +0000 (UTC), Go Linux wrote:

>>
> Why are you merging the debian, backports and dmo repos? Is there a way to separate them? I have rarely used > backports and always downloaded what I need from dmo when I first install and then disable it. dmo can really
> break things if you're not careful.
>>

> How do you receive updates and security fixes?

I generally don't. 'If it works, don't fix it' especially when it comes to complex media stuff. Case in point, I recently upgraded avidemux and dvdstyler for squeeze. Now the 'do not transcode' option is no longer checked by default in dvdstyler. That really sucks and there is no option to down grade.

>>
> Avidemux is in the dmo repos. The new 2.6* qt only version leaves a lot to be desired - a very long story that took > several weeks to figure out - so I took a chance and installed 2.5.6 Gtk from wheezy. Thankfully it works and I have > locked the version. Now is the time that I would want to disable the dmo repo and not have to worry about newer > versions of dependencies mucking things up. Is there a way to do that with the merged repos? Or will I just have to > be extra vigilant every time there are updates?
>>

>
> If I am not completely mistaken, there is no Avidemux
> package in the official Debian repositories, and there
> never has been.
>

This is true. I should have said I downloaded it from wheezy dmo repos. :)

>
> While I can well understand your stance
> on the 2.5.* --> 2.6.* Avidemux changes, there is not
> much one can do, except finding someone capable and
> willing to maintain the old GTK version (or even do it
> yourself, if that's an option).
>

Or find another video editor (ugh) or just keep wheezy and Jessie working for the duration. At my age it's a question of whether avidemux Gtk will outlast me or I'll outlast it!

>
> I decided to let go and let it R.I.P.
>

It was great while it lasted, wasn't it!! It took me days to to find all the deps and build the latest version from their git sources to fix the alsa default lockup (which required commenting out a line in a source file). Once I got it working I realized there was no cross fade in the qt version!! The dev's excuse was 'It's not easy to do with the 2.6 codebase'. How can anyone edit without a crossfade??

>
> However, in case you are dead set on completely disabling
> the dmo repo, you could probably make do with a bit of
> apt-pinning packages with the "-dmo*" version suffix.
> Yes, it's an ugly non-intuitive hack, and, even assuming
> it works as expected, it might not result in what you
> intended.
>

Probably not worth the effort.

>
> One more note: I have no evidence, it's really nothing
> more than just a gut feeling, but I expect less breakage
> to occur WRT dmo packages in the foreseeable future, since
> Debian returned to distributing ffmpeg instead of the
> libav fork (They did, didn't they?), and I am under the
> impression that a lot of the breakage was due to
> mismatches between those two.
>

FWIW. Avidemux builds ffmpeg into the app so doesn't require outside source. dvdstyer OTOH does require external ffmpeg.

Thanks for the detailed response. It was helpful if only to confirm what I suspected. At least I'm set for the next couple of years . . .

golinux