sigrok-cli: libsigrok and libsigrokdecode build dependencies should be unversioned

[Andreas Moog]

Imported from Debian bug http://bugs.debian.org/721581:

Package: sigrok-cli
Version: 0.4.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

rmadison -uqa -S -s unstable libsigrok libsigrokdecode
 libsigrok | 0.1.1-1 | sid | source
 libsigrok | 0.2.0-2 | sid | source
 libsigrok-dev | 0.2.0-2 | sid | amd64, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc
 libsigrok0 | 0.1.1-1 | sid | amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc
 libsigrok0-dev | 0.1.1-1 | sid | amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc
 libsigrok0-dev | 0.2.0-2 | sid | all
 libsigrok1 | 0.2.0-2 | sid | amd64, armhf, i386, ia64, mips, mipsel, powerpc, s390, s390x, sparc
 libsigrokdecode | 0.1.0-2 | sid | source
 libsigrokdecode | 0.2.0-2 | sid | source
 libsigrokdecode-dev | 0.2.0-2 | sid | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc
 libsigrokdecode0 | 0.1.0-2+b1 | sid | amd64, armel, armhf, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc
 libsigrokdecode0-dev | 0.1.0-2+b1 | sid | amd64, armel, armhf, hurd-i386, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc
 libsigrokdecode0-dev | 0.2.0-2 | sid | all
 libsigrokdecode1 | 0.2.0-2 | sid | amd64, armel, armhf, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, s390x, sparc

-- System Information:
Debian Release: wheezy/sid
  APT prefers precise-updates
  APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, 'precise-proposed'), (500, 'precise'), (100, 'precise-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 3.8.0-28-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

[Andreas Moog (ampelbein)]

This needs sigrok 0.2.0, see bug #1219613

[Andreas Moog (ampelbein)]

This is fixed in the current Ubuntu development release.