Status of {uni,multi}verse : 105 merges to do !

[Stefan Potyra]

Hi,

Am Mittwoch 04 Januar 2006 18:00 schrieb Stephan Hermann:
> Hi Lucas,
>
> On Wednesday 04 January 2006 01:36, Lucas Nussbaum wrote:
> > Hi,
> >
> > I generated a status of universe and multiverse :
> > http://ox.blop.info/bazaar/universe-versionslist.html.gz
> > Packages with the same version number are not displayed.
> >
> > There are still 105 packages that require a merge or a sync before
> > UVF... looks hard !
>
> Please please, speak to sistpoty....I like your work, but please let us
> coordinate the affords to bring those list to the usual places. For merges
> that is sistpoties tool at
> http://revu.tauware.de/~sistpoty/MoM/index.py?state=new

The merge-list is definitely no long term solution, and hopefully won't be 
needed for dapper+1 any more (hct/launchpad?).

First of all thanks Lucas, I like your list. I already added a link to it on 
the merge-list. 
However we need s.th. that keeps track of who is working on a package, which 
the merge list can fulfil. Thus was the original reason I wrote the 
merge-list, because someone else was working to merge a package, I was 
already working on. I hope that LP search can be used to achieve this, but I 
don't know if it's ready for this yet. 
Since we have worked with the merge-list up to now and only 11 days to get 
merges done are left, I would suggest to keep the merge-list as MOTU working 
tool and postpone the decision of moving to s.th. different for the merges of 
dapper + 1.

> Further I see debian package revision numbers, which are automatically
> synced during the time. Please check as well the assigned merges list on
> the same tool only with state=accepted

I guess there are two problems: 
1) packages are still marked as accepted which already have been updated in 
the archives (but maybe they haven't been built on all arches yet). Please 
everybody close the bugs for packages which really are fixed. If a package is 
falsely marked as accepted, just write a mail to me or even better to 
admin at tiber.tauware.de.

2) There are some (not many iirc) packages not covered by MoM-logs and thus 
won't hit the merge-list at all. I'll try to check/correct this tonight.

And finally there is the problem, that my time is currently limited (and thus 
I don't have time to update the merge-list every day). So dear tiber-admins, 
please help me with this (just see the 7 steps-howto I sent).

Looking ahead:
The next big thing we need to manage after UVF are packages with unmet 
dependencies. My proposal would be to also have a list similar to the 
merge-list for packages with unmet dependencies and also handle these by 
filing bugs in malone. However I would appreciate it, if s.o. was making a 
better suggestion or could even provide tools to handle this (since I won't 
need to write s.th. myself then :)

Cheers,
	Stefan.