Your message dated Mon, 13 Nov 2017 01:12:15 +0100
with message-id <[email protected]>
and subject line Re: Bug#881461: frei0r-plugins: Breaks frei0r-plugins (<= 
1.1.22)
has caused the Debian Bug report #881461,
regarding frei0r-plugins: Breaks frei0r-plugins (<= 1.1.22)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
881461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881461
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 (or
 ineffective)?

I typed

    $ apt-cache show frei0r-plugins

and read the "Breaks:" header.

* What was the outcome of this action?

Breaks: frei0r (<= 1.1.22)

* What outcome did you expect instead?

Breaks: frei0r-plugins (<= 1.1.22)


Thanks,
Kingsley

Bonus:  Tell me where to look for documentation on
        parameters and syntax for using frei0r effects as
        ffmpeg sources.

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages frei0r-plugins depends on:
ii  libc6                    2.24-17
ii  libcairo2                1.14.8-1
ii  libgavl1                 1.4.0-3
ii  libgcc1                  1:7.2.0-12
ii  libopencv-calib3d3.2     3.2.0+dfsg-3
ii  libopencv-contrib3.2     3.2.0+dfsg-3
ii  libopencv-core3.2        3.2.0+dfsg-3
ii  libopencv-features2d3.2  3.2.0+dfsg-3
ii  libopencv-flann3.2       3.2.0+dfsg-3
ii  libopencv-highgui3.2     3.2.0+dfsg-3
ii  libopencv-imgcodecs3.2   3.2.0+dfsg-3
ii  libopencv-imgproc3.2     3.2.0+dfsg-3
ii  libopencv-ml3.2          3.2.0+dfsg-3
ii  libopencv-objdetect3.2   3.2.0+dfsg-3
ii  libopencv-photo3.2       3.2.0+dfsg-3
ii  libopencv-shape3.2       3.2.0+dfsg-3
ii  libopencv-stitching3.2   3.2.0+dfsg-3
ii  libopencv-superres3.2    3.2.0+dfsg-3
ii  libopencv-video3.2       3.2.0+dfsg-3
ii  libopencv-videoio3.2     3.2.0+dfsg-3
ii  libopencv-videostab3.2   3.2.0+dfsg-3
ii  libopencv-viz3.2         3.2.0+dfsg-3
ii  libstdc++6               7.2.0-12

frei0r-plugins recommends no packages.

Versions of packages frei0r-plugins suggests:
pn  opencv-data  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Quoting Kingsley G. Morse Jr. (2017-11-13 00:50:47)
> > 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, and
> 
>     2.) failed to mention I assumed 
> 
>         a.) the "Breaks" header referred to a
>             non-existent package, and
> 
>         b.) what the original author meant was to say 
>             frei0r-plugins broke an *earlier version*
>             of itself.
> 
> So...
> 
> You were right!
> 
> I was wrong!
> 
> 
> But, but, but, I now find myself wondering if
> maybe the "Breaks:" header should just be removed.
> 
> Why?
> 
> If 
> 
>     a.) it doesn't make sense for a package to
>         break itself, then maybe
>         
>     b.) it also doesn't make sense for a package
>         to break its own source package.

It breaks a _previously_ existing binary package: See changelog, 
particularly for release 1.1.22git20090209-1.

The breaks hint is arguably harmless but can be dropped now, because the 
cnahce happened so long ago (and Debian does not support migrating 
directly from ancient releases to current one).

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

--- End Message ---
_______________________________________________
pkg-multimedia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Reply via email to