[opensuse-kde] Repo publish flags and upstream release management
So I just spent an afternoon trying to figure out why Choqok from KUP's plugins don't load, and it was the old chestnut that KPluginLoader doesn't permit plugins built with a newer version of kdelibs than is installed to load. This happened because Choqok in KUP built vs KDF is built vs the unpublished KDE 4.5.1 from KDF, and I still have KDE 4.5.0 installed. Can we make sure and disable publish in the dependent repositories of projects building vs KDF when we disable publish in KDF during integration of a new upstream version? This means 1) disable publish in all KDF repos 2) disable publish in KDE:Extra openSUSE_*_KDE_Distro_Factory 3) disable publish in KDE:Unstable:Playground I've made a feature request in the OBS to warn when not doing this: https://features.opensuse.org/310454 but until then please be careful. Will -- Will Stephenson, KDE Developer, openSUSE Boosters Team SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
2010/8/30 Will Stephenson
So I just spent an afternoon trying to figure out why Choqok from KUP's plugins don't load, and it was the old chestnut that KPluginLoader doesn't permit plugins built with a newer version of kdelibs than is installed to load.
This happened because Choqok in KUP built vs KDF is built vs the unpublished KDE 4.5.1 from KDF, and I still have KDE 4.5.0 installed.
Can we make sure and disable publish in the dependent repositories of projects building vs KDF when we disable publish in KDF during integration of a new upstream version?
This means
1) disable publish in all KDF repos 2) disable publish in KDE:Extra openSUSE_*_KDE_Distro_Factory 3) disable publish in KDE:Unstable:Playground
I've made a feature request in the OBS to warn when not doing this: https://features.opensuse.org/310454
but until then please be careful.
It's bnc#440894. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Mon, Aug 30, 2010 at 11:53 AM, Will Stephenson
So I just spent an afternoon trying to figure out why Choqok from KUP's plugins don't load, and it was the old chestnut that KPluginLoader doesn't permit plugins built with a newer version of kdelibs than is installed to load.
This happened because Choqok in KUP built vs KDF is built vs the unpublished KDE 4.5.1 from KDF, and I still have KDE 4.5.0 installed.
Can we make sure and disable publish in the dependent repositories of projects building vs KDF when we disable publish in KDF during integration of a new upstream version?
This means
1) disable publish in all KDF repos 2) disable publish in KDE:Extra openSUSE_*_KDE_Distro_Factory 3) disable publish in KDE:Unstable:Playground
I've made a feature request in the OBS to warn when not doing this: https://features.opensuse.org/310454
but until then please be careful.
Will
As I said in a comment on the feature request, I think it would be better if buildservice had a setting that project repositories could inherent their build and publish flags from the repositories they were built against, so if the repository they were built against gets disabled, the project repository does as well. This would, of course, be an option. As for packages that have those sorts of run-time dependency issues, shouldn't their spec file set the version of the library they were built against as a dependency? That way you wouldn't be able to install them unless the library was present. A lot of KDE packages do this already, which leads to a lot of annoying "Dependency not found" errors in YaST but that is better than a broken system. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Montag 30 August 2010 schrieb todd rme:
As I said in a comment on the feature request, I think it would be better if buildservice had a setting that project repositories could inherent their build and publish flags from the repositories they were built against, so if the repository they were built against gets disabled, the project repository does as well. This would, of course, be an option.
Repositories can have several paths, so inheritance is a bit complex to implement as you need to configure what's happening on conflict. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Tue, Aug 31, 2010 at 7:48 AM, Stephan Kulow
Am Montag 30 August 2010 schrieb todd rme:
As I said in a comment on the feature request, I think it would be better if buildservice had a setting that project repositories could inherent their build and publish flags from the repositories they were built against, so if the repository they were built against gets disabled, the project repository does as well. This would, of course, be an option.
Repositories can have several paths, so inheritance is a bit complex to implement as you need to configure what's happening on conflict.
Greetings, Stephan
True, but considering that having any of them disabled could very well break the binaries, I think if any of them is disabled the building would disable. For corner cases where you don't want this you can override it manually as people have to already. So doing it that way won't reduce functionality relative to what we have now, and would make things much easier in my opinion. It would also have to be something people would need to intentionally enable. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (4)
-
Cristian Morales Vega -
Stephan Kulow -
todd rme -
Will Stephenson