Bug#731836: libgavl1: raise priority to "optional"

[IOhannes m zmoelnig]

Package: libgavl1
Version: 1.4.0-1
Severity: minor

Dear Maintainer,
I noticed that this package has a priority "extra".

according to debian policy, i don't see a reason to not have priority
"optional", since the package does not have any "specialized requirements" such
as mentioned in §2.5 of the Debian policy.

the problem i'm experiencing is, that some packages of priority "optional"
depend on this package, which is a direct violation of §2.5 ("Packages must not
depend on packages with lower priority values").
so either these packages or your package ought to have fixed priorities, and i
think it that this package would be the better place 

quoting from #debian-mentors:

10:27 < zmoelnig> i'm wondering about the "priorities" field: which priority
	should i use as default for "most" packages? "extra" or "optional"?
[...]
10:30 < wRAR> zmoelnig: optional
[...]
10:31 < wRAR> there is #660249
10:31 < wRAR> the only example in the text (debug symbols) hints (at least for
	me) that this is not really about specialized software, but about
	non-software packages.
10:32 < wRAR> other widely used example is transitional packages
[...]
10:34 < wRAR> at this point someone usually remembers that distinctions between
	optional and extra do not have a real meaning and that priorities should
	be abolished.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.11-2-686-pae (SMP w/4 CPU cores)
Locale: LANG=de_AT.utf8, LC_CTYPE=de_AT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libgavl1 depends on:
ii  libc6              2.17-96
ii  multiarch-support  2.17-96

libgavl1 recommends no packages.

libgavl1 suggests no packages.

-- no debconf information