Hi Sebastian,
Thank you very much for sharing your thoughts.
It seems to me you asked a reasonable question:
> Why should frei0r-plugins break itself?
Through no fault of your own, when I filed the bug
report, I
1.) was unaware that a source package named
just "frei0r" existed,
Processing control commands:
> tags -1 + moreinfo
Bug #881461 [frei0r-plugins] frei0r-plugins: Breaks frei0r-plugins (<= 1.1.22)
Added tag(s) moreinfo.
--
881461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
On 2017-11-11 19:16:57, Kingsley G. Morse Jr. wrote:
> Package: frei0r-plugins
> Version: 1.6.1-1+b1
> Severity: minor
>
> Dear Maintainer,
>
> Thanks for maintaining frei0r's plugins.
>
> They look cool.
>
> * What led up to the situation?
>
> I wondered why
Package: frei0r-plugins
Version: 1.6.1-1+b1
Severity: minor
Dear Maintainer,
Thanks for maintaining frei0r's plugins.
They look cool.
* What led up to the situation?
I wondered why ffmpeg failed to use frei0r plugins
as ffmpeg sources.
* What exactly did you do (or not do) that was effective
