[opensuse-factory] Bison update in Factory
Hi all,
seems a few days ago we got a new Bison checkin into Factory, which
causes a bunch of fallouts (e.g. gstreamer-0.10, libgnomeprint are just
some I came across so far).
Not surprisingly, of course, those are 'no longer maintained' code bases
by their respective upstreams.
And I have, in all honesty, no idea about bison / flex / yacc syntax.
Anybody who know about this stuff willing to step up and help out
solving those issues?
Thanks a lot!
Dominique
NB: I really don't think we should unfreeze Factory 2 months prior to a
release. It makes stuff for devs focusing on 13.1 really nasty, as our
devel projects start failing for stuff which we do not have to worry
(yet) for 13.1.
Seeing this large 'diff' already shows that only part of the
contributors actually care for the releases / stabilisation period,
which is actually a shame.
--
Dimstar / Dominique Leuenberger
On 09/29/2013 04:07 PM, Dimstar / Dominique Leuenberger wrote:
Hi all,
seems a few days ago we got a new Bison checkin into Factory, which causes a bunch of fallouts (e.g. gstreamer-0.10, libgnomeprint are just some I came across so far).
Not surprisingly, of course, those are 'no longer maintained' code bases by their respective upstreams.
And I have, in all honesty, no idea about bison / flex / yacc syntax.
Anybody who know about this stuff willing to step up and help out solving those issues?
I was the one pushing it to Factory, so I'll ask coolo to revert the update and create a :Staging project so we can fix the fallout. Thanks. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Am 29.09.2013 16:24, schrieb İsmail Dönmez:
On 09/29/2013 04:07 PM, Dimstar / Dominique Leuenberger wrote:
Hi all,
seems a few days ago we got a new Bison checkin into Factory, which causes a bunch of fallouts (e.g. gstreamer-0.10, libgnomeprint are just some I came across so far).
Not surprisingly, of course, those are 'no longer maintained' code bases by their respective upstreams.
And I have, in all honesty, no idea about bison / flex / yacc syntax.
Anybody who know about this stuff willing to step up and help out solving those issues?
I was the one pushing it to Factory, so I'll ask coolo to revert the update and create a :Staging project so we can fix the fallout.
I reverted postgresql, bison and boost in factory - all three caused way too many regressions. postgresql was an obvious case of too little care on my side, but bison and boost looked reasonable at the times I checked them in. openSUSE:Factory:Staging is yours to watch. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Son, 2013-09-29 at 17:31 +0200, Stephan Kulow wrote:
I was the one pushing it to Factory, so I'll ask coolo to revert the update and create a :Staging project so we can fix the fallout.
I reverted postgresql, bison and boost in factory - all three caused way too many regressions. postgresql was an obvious case of too little care on my side, but bison and boost looked reasonable at the times I checked them in. openSUSE:Factory:Staging is yours to watch.
Don't worry: errors happen and the perfectly fast reaction after a
notification is more than enough to make up for it!
Thanks for you restless work and help!
Dominique
--
Dimstar / Dominique Leuenberger
On Sunday 29 September 2013 17:31:50 Stephan Kulow wrote:
I reverted postgresql, bison and boost in factory - all three caused way too many regressions. postgresql was an obvious case of too little care on my side, but bison and boost looked reasonable at the times I checked them in. openSUSE:Factory:Staging is yours to watch.
Hi Stephan, Thanks for this one. However I assume there is still one little breakage left and that is caused by the update of cyrus-sasl. This update causes kdepimlibs4 to fail due to an error in the include sasl.h. I did already some research on the internet and it seems it is a known issue and there is a small patch available. I have updated the package with this patch and submitted it to its devel repo (network). Regards Raymond -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Coolo wrote:
I reverted postgresql, bison and boost in factory - all three caused way too many regressions. postgresql was an obvious case of too little care on my side, but bison and boost looked reasonable at the times I checked them in. openSUSE:Factory:Staging is yours to watch.
I wanted to test a proposed fix ( https://github.com/yast/yast-core/pull/51 ) but yast2-core in Factory:Staging still uses bison-2.7: https://build.opensuse.org/package/rawlog/openSUSE:Factory:Staging/yast2-cor... The problem seems to be that bison-3.0 is checked in but has building disabled: https://build.opensuse.org/package/show/openSUSE:Factory:Staging/bison -- Martin Vidner, Cloud & Systems Management Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
On 02-Oct-13 3:46 PM, Martin Vidner wrote:
Coolo wrote:
I reverted postgresql, bison and boost in factory - all three caused way too many regressions. postgresql was an obvious case of too little care on my side, but bison and boost looked reasonable at the times I checked them in. openSUSE:Factory:Staging is yours to watch.
I wanted to test a proposed fix ( https://github.com/yast/yast-core/pull/51 ) but yast2-core in Factory:Staging still uses bison-2.7: https://build.opensuse.org/package/rawlog/openSUSE:Factory:Staging/yast2-cor...
The problem seems to be that bison-3.0 is checked in but has building disabled: https://build.opensuse.org/package/show/openSUSE:Factory:Staging/bison
coolo enabled it now. Thanks for the heads up! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 29 Sep 2013 15:07:41 +0200
Dimstar / Dominique Leuenberger
Hi all,
seems a few days ago we got a new Bison checkin into Factory, which causes a bunch of fallouts (e.g. gstreamer-0.10, libgnomeprint are just some I came across so far).
Not surprisingly, of course, those are 'no longer maintained' code bases by their respective upstreams.
And I have, in all honesty, no idea about bison / flex / yacc syntax.
Anybody who know about this stuff willing to step up and help out solving those issues?
Thanks a lot! Dominique
NB: I really don't think we should unfreeze Factory 2 months prior to a release. It makes stuff for devs focusing on 13.1 really nasty, as our devel projects start failing for stuff which we do not have to worry (yet) for 13.1. Seeing this large 'diff' already shows that only part of the contributors actually care for the releases / stabilisation period, which is actually a shame.
Hi, to see needed changes it depends what exact features given project use. But you can for inspiration look at my adaptation of yast ycp parser[1] ( yes, parser still lives for data files and backward compatibility for third party modules ). Josef [1] https://github.com/yast/yast-core/pull/51 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (7)
-
Dimstar / Dominique Leuenberger -
İsmail Dönmez -
İsmail Dönmez -
Josef Reidinger -
Martin Vidner -
Raymond Wooninck -
Stephan Kulow