Hi,
> > > > Some uwsgi-plugin-* packages have not been built for a reason I have
> > > > note been
> > > > able to understand. Anyway, they need to be given back.
> > > >
> > > > gb uwsgi-plugin-gccgo_0.0.2 . ANY
> > > > gb uwsgi-plugin-glusterfs_0.0.2 . ANY
> > > > gb uwsgi-plugin-lua_0.0.2 . ANY
> > > > gb uwsgi-plugin-psgi_0.0.2 . ANY
> > > > gb uwsgi-plugin-python_0.0.2 . ANY
> > > > gb uwsgi-plugin-rados_0.0.2 . ANY
> > >
> > > They can't be given back as they don't exist in the database. So that
> > > needs to be debugged first.
> >
> > If this can help, those new source packages build binary packages that were
> > previously built by src:uwsgi. For instance, src:uwsgi-plugin-gccgo builds
> > uwsgi-plugin-gccgo. uwsgi-plugin-gccgo was built by src:uwsgi in previous
> > versions.
> > there is no problem, they were correctly built (uwsgi-plugin-{java,ruby}
> > and uwsgi-plugin-pypy is completely new).
>
> Thanks for the details. The problem is that those new packages are using
> a lower version than uwsgi for the their source version and wanna-build
> has no way to guess that the binary packages it produces are in a
> different version.
>
> I have fixed this by manually injecting those packages in the database.
There seems to be still missing builds for these packages for:
armel armhf i386 riscv64
Alex
