On 3/18/2010 at 16:55, James Ogley
wrote: you submitted gwibber to openSUSE:FActory with: +- Added Requires: python-desktopcouch. But that package - and it's dependencies - is not yet in openSUSE:Factory. Without that requires, someone doing an update will get a non-functioning gwibber since it was already updated to the couch-dependent version.
If the couch stack's not going into Factory, gwibber *must* be downgraded back to the 2.0 packages I submitted a while ago, newer versions have a hard dependency on couch.
I think getting couch into Factory should not be the biggest of our worries / problems. Somebody already got a package around that we can just take, cleanup and forward? (Even better if we can skip the cleanup part). I'll work on this asap. Keeping the old packages around even for a release (which is still a long way to go) is certainly not the best way to go forward...
From a packagers point of view, it would be great if there would be sort of ./configure that verifies at least if the system has all it needs. This would certainly help avoiding such packages from even enter the repos. (this configure would not have to do very much, just check if all of the py imports are possible to be satisfied).
For the future, to avoid such breakage, it might be nice if a 'lint' or similar that could do a dummy python script with all the imports it can possibly find in the various .py files and see if this can pass (sounds gibberish and probably is... the smart guys can work this out :) ). Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org