Does libgpod have a (pro)active maintainer in Core?

[Jeff Spaleta]

There are a couple of issues with libgpod that are affecting multiple
packages in Extras and Core at the moment that I want to make sure
people are aware about the problem.  An upgrade to the latest version
needs to be considered for at least fc6, and there needs to be a
decision on how to handle the currently unshipped python bindings.

Looking at the currently open bugs on thses issues (one dating back to
May and another to July) I haven't seen any discussion from anyone in
the package changelog that could be considered an active maintainer
for this package. Also it appears the bugreports are assigned to
someone who isn't in the changelog so far.  As a result, I'm bring the
state of this package up to the general maintainer list because it
appears to me that maintainership of libgpod is in a virtual limbo and
the bugzilla based communication has broken down because its not
getting to the maintainers who have a vested interest in pushing
builds of this.  This package represents important functionality for a
growing number of audio applications in the Fedora Package space..


Two questions:
1) Can we get an updated in fc6/fc5 in coordination with the needs of
community packagers in Extras.

2) The python bindings that come with the libgpod need to be built
atleast for development trees (and again for release trees if libgpod
gets updated there). There needs to be an understanding as to whether
or not Extras maintainers should be dealing with the bindings as a
separate srpm (even though its part of the upstream 0.4 release)


Bug report references with date of filing:
2006-07-11:  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=198582
2006-10-20:  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211648

These are related rhythmbox reports::
2006-05-27:  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=193413
2006-10-23:  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=211823


-jef"Please tell me that the maintainership state of libgpod has
fallen through the cracks by accident and its state of disrepair isn't
a delibrate decision, and fixing this is just a matter of clearing up
who has the time and access to start pushing up test updates with the
python bindings enabled."spaleta