[pkg-ggz-maintainers] Next uploads, and news

[Peter Eisentraut]

Josef Spillner wrote:
> All of the 3 most recent uploads were accepted!
> From looking at which packages are left, I'd prioritise as follows:
>
> Urgent:
>  * user clients and games: ggz-{gtk,kde}-{client,games}, that's 4
> packages * ggz-python
> Not so urgent:
>  * text client, server, sdl-games

Here is how it looks:

libggz-0.0.13.tar.gz             DONE
ggz-client-libs-0.0.13.tar.gz    DONE
ggz-server-0.0.13.tar.gz         package name/soname mismatch(*)
ggz-txt-client-0.0.13.tar.gz     uploaded, in NEW
ggz-gtk-client-0.0.13.tar.gz     binary packages need to be split(*)
ggz-kde-client-0.0.13.tar.gz     libasound2-dev not installable
ggz-gnome-client-0.0.13.tar.gz   DONE
ggz-gtk-games-0.0.13.tar.gz      uploaded, in NEW
ggz-kde-games-0.0.13.tar.gz      libasound2-dev not installable
ggz-sdl-games-0.0.13.tar.gz      libasound2-dev not installable
ggz-python-0.0.13.tar.gz         waiting for -server
ggz-utils-0.0.13.tar.gz          DONE
ggz-grubby-0.0.13.tar.gz         DONE
ggz-docs-0.0.13.tar.gz           DONE
ggz-community-0.0.13.tar.gz      no packaging in svn
ggz-java-0.0.13.tar.gz           no packaging in svn

The items marked (*) need extra packaging work that I detailed earlier.  
The libasound2-dev issue might be a temporary problem in pbuilder or 
the mirror I'm using.  I'll try again over the next few days.  The 
packages themselves look OK.

> After all uploads are done, there are a number of changes to the
> files resulting in 0.0.13-2 packages which would require a reupload
> of everything. I assume this will be much faster as it doesn't go
> through the NEW queue.

Yes.  Let's talk about using cdbs then, too.