[opensuse-gnome] gwibber and desktopcouch
Magnus, you submitted gwibber to openSUSE:FActory with: +- Added Requires: python-desktopcouch. But that package - and it's dependencies - is not yet in openSUSE:Factory. I propose to submit those packages first and only submit the new gwibber once all dependencies are checked in. So, for now I propose to revoke the gwibber submit - and submit desktopcouch, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
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. -- James Ogley (riggwelter) openSUSE Member GNOME Team and Planet SUSE e: riggwelter@opensuse.org w: http://opensuse.org/GNOME t: @riggwelter w: http://www.planetsuse.org openSUSE: Get It, Discover It, Create It at http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Thursday 18 March 2010 16:55:14 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.
Ah, so the package is already broken and shouldn't have been submitted at all since desktopcouch was not in yet ;-( That's bad - so it's even more important to get the stack in. Let's get it in asap so that gwibber runs again, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 3/18/2010 at 16:55, James Ogley <riggwelter@opensuse.org> 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
On Thursday 18 March 2010 17:05:32 Dominique Leuenberger wrote:
On 3/18/2010 at 16:55, James Ogley <riggwelter@opensuse.org> 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.
Check: home:FunkyPenguin:Gwibber-couch/ I even took care that the packages build for Factory but haven't tested them at all - and I don't want to maintain them.
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 :) ).
Yeah, something like that would help, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 3/18/2010 at 17:23, Andreas Jaeger <aj@novell.com> wrote: On Thursday 18 March 2010 17:05:32 Dominique Leuenberger wrote:
On 3/18/2010 at 16:55, James Ogley <riggwelter@opensuse.org> 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.
Check: home:FunkyPenguin:Gwibber-couch/
I even took care that the packages build for Factory but haven't tested them
I used osc search python-desktopcouch and it showed my a package by Riggwelter (Isn't that James?) I already copypac'ed it to my branch and am busy fixing it up for Factory (only minor tweakings needed). name wise python-desktopcouch sounds more reasonable than gwibber-couch (it's not only for gwibber after all). At the current pace I expect that I can submit it to devel:languages:python later this evening. (I don't think the GNOME: namespace is the right one. Just because a G-app is the first consumer doesn't make that specific lib a G-lib). Dominqiue -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Thursday 18 March 2010 17:27:24 Dominique Leuenberger wrote:
On 3/18/2010 at 17:23, Andreas Jaeger <aj@novell.com> wrote: [...] Check: home:FunkyPenguin:Gwibber-couch/
I even took care that the packages build for Factory but haven't tested them
I used osc search python-desktopcouch and it showed my a package by Riggwelter (Isn't that James?) I already copypac'ed it to my branch and am busy fixing it up for Factory (only minor tweakings needed).
Yes, that's James. You might want to look at FunkyPenguin's package as well. You need AFAIK all the packages from FunkyPenguin's project, including erlang.
name wise python-desktopcouch sounds more reasonable than gwibber-couch (it's not only for gwibber after all).
I agree.
At the current pace I expect that I can submit it to devel:languages:python later this evening. (I don't think the GNOME: namespace is the right one. Just because a G-app is the first consumer doesn't make that specific lib a G-lib).
And then submit to factory ;) Thanks, Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 3/18/2010 at 17:37, Andreas Jaeger <aj@novell.com> wrote: I used osc search python-desktopcouch and it showed my a package by Riggwelter (Isn't that James?) I already copypac'ed it to my branch and am busy fixing it up for Factory (only minor tweakings needed).
Yes, that's James. You might want to look at FunkyPenguin's package as well.
:( python-desktopcouch != couchdb and gwibber actually requires couchdb AND desktopcouch (desktopcouch probably should also fail without couchdb, which it does not at the moment... we really need that lint :) )
You need AFAIK all the packages from FunkyPenguin's project, including erlang.
yes, erlang is needed to build couchdb (which, btw, is an apache project).
At the current pace I expect that I can submit it to devel:languages:python later this evening. (I don't think the GNOME: namespace is the right one. Just because a G-app is the first consumer doesn't make that specific lib a G-lib).
And then submit to factory ;)
Certainly... the stack seems rather big. Something to do :) CALL FOR VOLUNTEERS! The packages seem around, just cleanup is needed. Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On 18 March 2010 16:44, Dominique Leuenberger <Dominique.Leuenberger@tmf-group.com> wrote:
On 3/18/2010 at 17:37, Andreas Jaeger <aj@novell.com> wrote: I used osc search python-desktopcouch and it showed my a package by Riggwelter (Isn't that James?) I already copypac'ed it to my branch and am busy fixing it up for Factory (only minor tweakings needed).
Yes, that's James. You might want to look at FunkyPenguin's package as well.
:( python-desktopcouch != couchdb and gwibber actually requires couchdb AND desktopcouch (desktopcouch probably should also fail without couchdb, which it does not at the moment... we really need that lint :) )
You need AFAIK all the packages from FunkyPenguin's project, including erlang.
yes, erlang is needed to build couchdb (which, btw, is an apache project).
At the current pace I expect that I can submit it to devel:languages:python later this evening. (I don't think the GNOME: namespace is the right one. Just because a G-app is the first consumer doesn't make that specific lib a G-lib).
And then submit to factory ;)
Certainly... the stack seems rather big. Something to do :) CALL FOR VOLUNTEERS! The packages seem around, just cleanup is needed.
Dominique
-- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
I knocked the stack up in a pretty quick space of time, not really expecting the amount of pain it has dished out. There are differences between the desktopcouch package in my repo vs Riggwelter's - I have implemented the sub packages so that we follow the other distros like Fedora and Ubuntu. I have also borrowed from Fedora the spec files for couchdb etc. Darix did do some work on some of the packages too (can't remember which ones now). I just haven't had the time to look at it, but also more importantly I think it might be a bit beyond my simple packaging knowledge. The big issue I think is CouchDB, and talking to both the Gwibber devs and also the desktopcouch devs CocuhDB isnt the friendliest of packages regardless of distro. Remember the Rodrigo is doing a lot with desktopcouch so if need be we could always try and speak to him nicely :-) Regards, Andy -- Andrew Wafaa IRC: FunkyPenguin PGP: 0x3A36312F openSUSE: Get It, Discover It, Create It at http://www.opensuse.org
Hi Andreas, On Thu, 2010-03-18 at 14:58 +0100, Andreas Jaeger wrote:
Magnus,
you submitted gwibber to openSUSE:FActory with: +- Added Requires: python-desktopcouch.
Ops :-)
But that package - and it's dependencies - is not yet in openSUSE:Factory.
I propose to submit those packages first and only submit the new gwibber once all dependencies are checked in. So, for now I propose to revoke the gwibber submit - and submit desktopcouch,
I revoked the request while we work on getting all the dependencies into oS:F. Cheers, Magnus -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On 3/18/2010 at 21:05, Magnus Boman <captain.magnus@gmail.com> wrote:
I revoked the request while we work on getting all the dependencies into oS:F.
Which can be a long shot. The dependencies did, for such a small application, become enormous. And even though I have a fuil stack building in my branch, it is not functional yet. (Most packages are not ready for oS:F submission and need some / a lot of cleanup; if somebody wants to work on it, just let me know: access to those packages should not be a problem. For now they live in my home: namespace) Unfortunately, all the various error messages it can produce at start up seem not to be unknown to upstream and all of them are filed in lp. So all in all: 2.29.x of gwibber will take a while to become fully operational again. I subscribed to the various lp bugs and hope to get it running soon (and now: 2.29.92.1 did not change much). Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On 3/18/2010 at 14:58, Andreas Jaeger <aj@novell.com> wrote: Magnus,
you submitted gwibber to openSUSE:FActory with: +- Added Requires: python-desktopcouch.
But that package - and it's dependencies - is not yet in openSUSE:Factory.
I propose to submit those packages first and only submit the new gwibber once all dependencies are checked in. So, for now I propose to revoke the gwibber submit - and submit desktopcouch,
Andreas, All, We got a good step further and all the packages required for the stack ended up and have been accepted in the respective devel projects where they make sense. Many of the packages got some cleanup and fixing. It would be great if the people responsible for the respective repositories / packages could push them forward to Factory, so that testing of gwibber by the community can start as soon as possible. The Projects / Packages are (I hope not to miss any): server:database / couchdb devel:languages:erlang / erlang devel:languages:python / python-oauth devel:languages:python / python-couchdb devel:languages:python / python-desktopcouch Thank you all! Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
On Monday 29 March 2010 14:30:51 Dominique Leuenberger wrote:
On 3/18/2010 at 14:58, Andreas Jaeger <aj@novell.com> wrote: Magnus,
you submitted gwibber to openSUSE:FActory with: +- Added Requires: python-desktopcouch.
But that package - and it's dependencies - is not yet in openSUSE:Factory.
I propose to submit those packages first and only submit the new gwibber once all dependencies are checked in. So, for now I propose to revoke the gwibber submit - and submit desktopcouch,
Andreas, All,
We got a good step further and all the packages required for the stack ended up and have been accepted in the respective devel projects where they make sense. Many of the packages got some cleanup and fixing.
It would be great if the people responsible for the respective repositories / packages could push them forward to Factory, so that testing of gwibber by the community can start as soon as possible.
The Projects / Packages are (I hope not to miss any): server:database / couchdb devel:languages:erlang / erlang devel:languages:python / python-oauth devel:languages:python / python-couchdb devel:languages:python / python-desktopcouch
Great! Will you ping the owners or you need help? Andreas -- Andreas Jaeger, Program Manager openSUSE, aj@{novell.com,opensuse.org} Twitter: jaegerandi | Identica: jaegerandi SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On 3/29/2010 at 14:43, Andreas Jaeger <aj@novell.com> wrote: It would be great if the people responsible for the respective repositories / packages could push them forward to Factory, so that testing of gwibber by the community can start as soon as possible.
The Projects / Packages are (I hope not to miss any): server:database / couchdb devel:languages:erlang / erlang devel:languages:python / python-oauth devel:languages:python / python-couchdb devel:languages:python / python-desktopcouch
Great!
Will you ping the owners or you need help?
There should have been at least one maintainer of each prj in the CC list, but I'll try to ping 'more frequently' on various users. If I do not succeed by the end of the week I'll get back to you. Thanks a lot! Dominique -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org
participants (5)
-
Andreas Jaeger -
Andrew Wafaa -
Dominique Leuenberger -
James Ogley -
Magnus Boman