as per $summary Committed today. Minor fixes wrt v1.3.1 * dropped qml use flag ( masked since the very beginning ) * Minor fix in translations installation I consider the above fixes rather trivial so please proceed with the stabilization Test: A compile test should be fine but make sure that you use at least one of the supported LINGUAS e.g LINGUAS="it de" emerge -av qt-creator Thanks
> I consider the above fixes rather trivial so please proceed with the In my case the ebuild is not working perfect (for updates?) because qt-docs make some problems as mentionened here http://forums.gentoo.org/viewtopic-t-830851-highlight-qtcreator.html and upstream bug is also related http://bugreports.qt.nokia.com/browse/QTCREATORBUG-315 I thought doc patch of 1.2.1 is related and working but I could not manage to work with 1.3.1-r1. Maybe someone else has more ebuild experience and/or time.
(In reply to comment #1) > > I consider the above fixes rather trivial so please proceed with the > > In my case the ebuild is not working perfect (for updates?) because qt-docs > make some problems as mentionened here > http://forums.gentoo.org/viewtopic-t-830851-highlight-qtcreator.html > and upstream bug is also related > http://bugreports.qt.nokia.com/browse/QTCREATORBUG-315 > > I thought doc patch of 1.2.1 is related and working but I could not manage to > work with 1.3.1-r1. Maybe someone else has more ebuild experience and/or time. > Please this is not a place to report bugs for qt-creator Your problem has been reported to this bugzilla again and closed as upstream http://bugs.gentoo.org/show_bug.cgi?id=308563 Please do not report bugs about qt-creator here. Open new bugs are make them blockers to this one Furthermore that docs patch is for fix the documentation installation path and not for disabling or fixing the qt-doc issue reported upstream Either poke upstream to fix the sqlite issue or comment on our bug if you feel like it.
Should arch teams proceed anyway? Is this a regression over current stable?
Please proceed
amd64 stable
(In reply to comment #2) > Please this is not a place to report bugs for qt-creator Sorry, my comment should not be a bug report, only a reason to keep portage stable stable. I think stable marked packages should work stable, not only install without flaws. If there are major (I think it is) upstream bugs who will need this version in portage? Is it all about a number? I would appreciate if the maintainers keep on there good work by providing ebuilds for newer versions but display a comment after merge if a bug and maybe a workaround exist. I cannot even use qt-creator 1.2.1 with the Help Plugin acctivated after trying 1.3.1-r1. A no go for a productive system.
(In reply to comment #6) > (In reply to comment #2) > > Please this is not a place to report bugs for qt-creator > Sorry, my comment should not be a bug report, only a reason to keep portage > stable stable. I think stable marked packages should work stable, not only > install without flaws. If there are major (I think it is) upstream bugs who > will need this version in portage? Is it all about a number? > > I would appreciate if the maintainers keep on there good work by providing > ebuilds for newer versions but display a comment after merge if a bug and maybe > a workaround exist. > I cannot even use qt-creator 1.2.1 with the Help Plugin acctivated after trying > 1.3.1-r1. A no go for a productive system. > I cant reproduce the bug, none of the Qt members does, upstream claims it is not reproducible always ( rarely if I may say ). What kind of message would you prefer? About the doc use flag?
(In reply to comment #7) > (In reply to comment #6) > I cant reproduce the bug, none of the Qt members does, upstream claims it is > not reproducible always ( rarely if I may say ). My installation is working again since world update today. > What kind of message would you prefer? About the doc use flag? Just a hint that an upstream bug is known, a link to bug report and the possible work around (-noload Help) if exists. If possible with a "Do you realy want to install/abort" dialogue. This could prevent users from destroying their daily needed tools and will affirm Gentoo as the best distribution on earth 8)
Archtested on x86: Looks good now. Although It did not want to start in the beginning, and would just occupy once cpu forever and do nothing. After starting it once as root it works fine now also for users and I can't reproduce the problem.
stable x86, thanks Thomas
ppc stable
ppc64 stable
