The purpose of this bug is to: - Comment issues that will need to be covered in future Gnome 2.32 Upgrade guide. - Add bugs that will need to be covered here as blockers of this bug Thanks Reproducible: Always
A first try in: http://dev.gentoo.org/~pacho/gnome-2.32-upgrade.xml
(In reply to comment #1) > A first try in: > http://dev.gentoo.org/~pacho/gnome-2.32-upgrade.xml > If you are ok with this, I will be happy to commit and prepare the news item.
I'd rather use the gconftool command I gave in the gnome-panel bug report. Otherwise looks good. If you wish, you can add a paragraph about how we tried to support multiple python slots (multiple slot 2 or/and 3) but how it most likely isn't ready yet for prime time.
(In reply to comment #3) > I'd rather use the gconftool command I gave in the gnome-panel bug report. > Otherwise looks good. > The problem of gconftool command is that nobody has tried it it really fixes the problem since I solved it in my setup simply removing offending file :-/ > If you wish, you can add a paragraph about how we tried to support multiple > python slots (multiple slot 2 or/and 3) but how it most likely isn't ready yet > for prime time. > I think that, from a Gnome point of view, most of apps should compile and work even setting python3 as main interpreter but since there are still a lot of other packages still not supporting it, I wouldn't mention it as, otherwise, some people could try to set python3 as main and see other non-Gnome packages failing to build or run
A recursive unset starting at the root of the gconf path specified in that file should do the job if we can't find anything more specific.(In reply to comment #4) > (In reply to comment #3) > > I'd rather use the gconftool command I gave in the gnome-panel bug report. > > Otherwise looks good. > > > > The problem of gconftool command is that nobody has tried it it really fixes > the problem since I solved it in my setup simply removing offending file :-/ A recursive unset starting at the root of the gconf path specified in that file should do the job if we can't find anything more specific. > > If you wish, you can add a paragraph about how we tried to support multiple > > python slots (multiple slot 2 or/and 3) but how it most likely isn't ready yet > > for prime time. > > > > I think that, from a Gnome point of view, most of apps should compile and work > even setting python3 as main interpreter but since there are still a lot of > other packages still not supporting it, I wouldn't mention it as, otherwise, > some people could try to set python3 as main and see other non-Gnome packages > failing to build or run well I wanted the paragraph especially for telling users it's not ready and they should not complain :).
(In reply to comment #5) > > (In reply to comment #3) > > > I'd rather use the gconftool command I gave in the gnome-panel bug report. > > > Otherwise looks good. > > > > > > > The problem of gconftool command is that nobody has tried it it really fixes > > the problem since I solved it in my setup simply removing offending file :-/ > > A recursive unset starting at the root of the gconf path specified in that > file should do the job if we can't find anything more specific. > I have just run the following: gconftool-2 --recursive-unset /apps/panel And looks like all my panel configuration have been reset... I think it's too drastic :-/ > well I wanted the paragraph especially for telling users it's not ready and > they should not complain :). > Nice but, if I don't misremember, python3 news item was already created suggesting people to not set it as main interpreter, then, this could be a bit redundant, but I can try to add it if you want
(In reply to comment #6) > (In reply to comment #5) > > > (In reply to comment #3) > > > > I'd rather use the gconftool command I gave in the gnome-panel bug report. > > > > Otherwise looks good. > > > > > > > > > > The problem of gconftool command is that nobody has tried it it really fixes > > > the problem since I solved it in my setup simply removing offending file :-/ > > > > A recursive unset starting at the root of the gconf path specified in that > > file should do the job if we can't find anything more specific. > > > > I have just run the following: > gconftool-2 --recursive-unset /apps/panel > > And looks like all my panel configuration have been reset... I think it's too > drastic :-/ it's either that or freezing panel, remember :) It's the best we can do if nobody wants to give us more info. > > well I wanted the paragraph especially for telling users it's not ready and > > they should not complain :). > > > > Nice but, if I don't misremember, python3 news item was already created > suggesting people to not set it as main interpreter, then, this could be a bit > redundant, but I can try to add it if you want well, it's also about USE_PYTHON for people who would like gracious python migrations for example.
(In reply to comment #7) > it's either that or freezing panel, remember :) It's the best we can do if > nobody wants to give us more info. > But looks like simply removing offending file: rm -f ~/.gconf/desktop/gnome/interfaces/%gconf.xml makes panel happy and don't lose panel configuration. > > > well I wanted the paragraph especially for telling users it's not ready and > > > they should not complain :). > > > > > > > Nice but, if I don't misremember, python3 news item was already created > > suggesting people to not set it as main interpreter, then, this could be a bit > > redundant, but I can try to add it if you want > > well, it's also about USE_PYTHON for people who would like gracious python > migrations for example. > In that case I would also need a bit of help since I don't even know how to use "USE_PYTHON" and co. :-(, if you want, you can simply provide plain text and I can move it to the doc file. Thanks a lot
I have just added a note referring to python3 being used as main interpreter... if you have any suggestions to improve it, please tell me
ACK for the python paragraph. I'm still working on the evolution migration fix script, only de-duplication of system entry left and I'll attach it here.
Created attachment 262523 [details] fix-addressbook.py this little script should fix evolution migration problems. It removes uri attribute from local addressbooks (it is deprecated from my testings) and it removes the extra(s?) system addressbooks that could have been created by selecting those not part of the group with the most local addressbooks . In other words, if you have one in its own group and another with a couple of others, it will select the one alone for removal.
Sadly my addressbook was already fixed manually, then, I cannot test if this will fix that breakages but, at least, I have tried to run it and my addressbook is still ok :-) Thanks a lot for the script. One last doubt about the guide: How should we provide this script? Should I point people to download it from here or from dev.gentoo.org/~pacho/...? Or should we even provide it with evolution installation?
Pointing them to the bug report should be fine, there should not be a lot of people that would need it. And for the record I wrote this script to fix my own broken setup :).
http://dev.gentoo.org/~pacho/gnome-2.32-upgrade.xml -> updated
Fixed