RFS: audacious/3.6.2-2~bpo8+1 and audacious-plugins/3.6.2-2~bpo8+1

[Nicholas D Steeves]

On 6 May 2016 at 05:51, Mattia Rizzolo <mattia at debian.org> wrote:
> On Wed, May 04, 2016 at 11:32:20PM -0400, Nicholas D Steeves wrote:
>> /usr/include/roaraudio.h is found in libroar-dev.  Libroar-dev is not
>> a build dependency of either a audacious or audacious-plugins;
>> likewise, libroar2 is not a runtime dependency.  Have you added extra
>> packages to your clean chroot?
>
> definitely not.
>
>> A formal backport in a clean chroot+local repository so
>> audacious-plugins can build against the backported audacious worked
>> for me.
>
> I tried now the very packages you uploaded there, and failed the same.
> Some things:
>
> in sid there is a *real* libsndio-dev, but that package is not in
> jessie.  Instead, in jessie the only thing providing that package is
> libroar-dev.
>
> Which rises the question: do *you* a clean chroot?
> My chroot is a simple jessie, + the jessie-bpo and the local repo added,
> and the only things installed from outside jessie are the binaries built
> by the locally backported audacious.

Oh my, this is embarrassing!  As I mentioned before my chroot uses the
following:
OTHERMIRROR='deb http://security.debian.org/ jessie/updates main | deb
http://debian.ec.as6453.net/debian/ jessie-backports main | deb
[trusted=yes] file:/usr/src/repo/amd64 ./'

It seems I backported libsndio in a fugue state Feb 9th!  I found a
libsndio-dev_1.0.1-2~bpo8+1_amd64.deb in my local repo.  I can't find
an email notification from debian-mentors saying I uploaded it, so my
conclusion is that this was leftover cruft from when I just starting
out.  You have my sincerest apologies.  I've just purged that repo and
uploaded a bpo of libsndio to mentors.

In the interest of preventing future mistakes, could someone please
reply to my git question from the following email:
Message-ID: <CAD=QJKhx07NQ17gNOEowi24VDreHY-nj52UNCTrv1e1UiSAZzw at mail.gmail.com>

Humble regards,
Nicholas