[opensuse-kde] Different vendor for KDE:KDE4:Playground
Hi guys. Could you please be so kind to use a different vendor for the KDE:KDE4:Playground repo than for the stable ones? Reasoning is that with K:K:P added I get updated to beta versions from e.g. Amarok & Ktorrent while being unable to prevent that somehow which currently forces me to constantly enable & disable the repo which is a pita. Thanks a lot, Stephan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Hi!
Could you please be so kind to use a different vendor for the KDE:KDE4:Playground repo than for the stable ones?
Reasoning is that with K:K:P added I get updated to beta versions from e.g. Amarok & Ktorrent while being unable to prevent that somehow which currently forces me to constantly enable & disable the repo which is a pita.
While I agree with you that this would be useful, there is a workaround. For the packages you have installed and do not want to upgrade to Playground add a lock zypper al -r Name-of-Playground-repo packagename for each package. Christian -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Freitag, 12. Februar 2010 08:54:14 schrieb Christian Trippe:
Hi!
Could you please be so kind to use a different vendor for the KDE:KDE4:Playground repo than for the stable ones?
Reasoning is that with K:K:P added I get updated to beta versions from e.g. Amarok & Ktorrent while being unable to prevent that somehow which currently forces me to constantly enable & disable the repo which is a pita.
While I agree with you that this would be useful, there is a workaround.
For the packages you have installed and do not want to upgrade to Playground add a lock
zypper al -r Name-of-Playground-repo packagename
for each package.
JFYI, to fullfill this request, someone has to run osc signkey --create KDE:KDE4:Playground the new and own key will lead to an own vendor as well. I will create a fate request that we get key managing features in webui ... -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Friday 12 of February 2010, Adrian Schröter wrote:
Am Freitag, 12. Februar 2010 08:54:14 schrieb Christian Trippe:
Hi!
Could you please be so kind to use a different vendor for the KDE:KDE4:Playground repo than for the stable ones?
Reasoning is that with K:K:P added I get updated to beta versions from e.g. Amarok & Ktorrent while being unable to prevent that somehow which currently forces me to constantly enable & disable the repo which is a pita.
JFYI, to fullfill this request, someone has to run
osc signkey --create KDE:KDE4:Playground
the new and own key will lead to an own vendor as well.
I don't understand why we should solve this by having a separate vendor and not e.g. repo priorities. What exactly is the purpose of having a different vendor? It's very likely that we either should not do this or do it for more subrepositories of KDE: . -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak@suse.cz , l.lunak@kde.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Friday February 12 2010 16:35:14 Lubos Lunak wrote:
On Friday 12 of February 2010, Adrian Schröter wrote:
Am Freitag, 12. Februar 2010 08:54:14 schrieb Christian Trippe:
Hi!
Could you please be so kind to use a different vendor for the KDE:KDE4:Playground repo than for the stable ones?
Reasoning is that with K:K:P added I get updated to beta versions from e.g. Amarok & Ktorrent while being unable to prevent that somehow which currently forces me to constantly enable & disable the repo which is a pita.
JFYI, to fullfill this request, someone has to run
osc signkey --create KDE:KDE4:Playground
the new and own key will lead to an own vendor as well.
I don't understand why we should solve this by having a separate vendor and not e.g. repo priorities. What exactly is the purpose of having a different vendor? It's very likely that we either should not do this or do it for more subrepositories of KDE: .
Priorities are repository wide. So it weren't possible to use e.g. Amarok from K:K:P while sticking to the Ktorrent from K:K:F:D. Because vendors are set for every package the above usecase weren't a problem with different vendors. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
Am Freitag, 12. Februar 2010 16:40:36 schrieb Stephan Kleine:
On Friday February 12 2010 16:35:14 Lubos Lunak wrote:
On Friday 12 of February 2010, Adrian Schröter wrote:
Am Freitag, 12. Februar 2010 08:54:14 schrieb Christian Trippe:
Hi!
Could you please be so kind to use a different vendor for the KDE:KDE4:Playground repo than for the stable ones?
Reasoning is that with K:K:P added I get updated to beta versions from e.g. Amarok & Ktorrent while being unable to prevent that somehow which currently forces me to constantly enable & disable the repo which is a pita.
JFYI, to fullfill this request, someone has to run
osc signkey --create KDE:KDE4:Playground
the new and own key will lead to an own vendor as well.
I don't understand why we should solve this by having a separate vendor and not e.g. repo priorities. What exactly is the purpose of having a different vendor? It's very likely that we either should not do this or do it for more subrepositories of KDE: .
Priorities are repository wide. So it weren't possible to use e.g. Amarok from K:K:P while sticking to the Ktorrent from K:K:F:D.
Because vendors are set for every package the above usecase weren't a problem with different vendors.
Vendors give the user the chance to decide which version of a package to pick. Also zypper/yast are showing when a package changes the Vendor. So the user has a chance to decide on his own. Vendors are about trust in the end. For example a user might be fine to use $unimportant_small_application from Playground, but he may not be fine to use kdebase from there. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Saturday 13 of February 2010, Adrian Schröter wrote:
Am Freitag, 12. Februar 2010 16:40:36 schrieb Stephan Kleine:
On Friday February 12 2010 16:35:14 Lubos Lunak wrote:
I don't understand why we should solve this by having a separate vendor and not e.g. repo priorities. What exactly is the purpose of having a different vendor? It's very likely that we either should not do this or do it for more subrepositories of KDE: .
Priorities are repository wide. So it weren't possible to use e.g. Amarok from K:K:P while sticking to the Ktorrent from K:K:F:D.
Because vendors are set for every package the above usecase weren't a problem with different vendors.
Vendors give the user the chance to decide which version of a package to pick.
Also zypper/yast are showing when a package changes the Vendor. So the user has a chance to decide on his own.
Vendors are about trust in the end. For example a user might be fine to use $unimportant_small_application from Playground, but he may not be fine to use kdebase from there.
Ok, whatever, but then this is not just about Playground. I may not want to use something from Community, or from Factory, or from UNSTABLE or maybe somewhere else. So which all repos should have their own vendor? - Playground - Community - UNSTABLE - Factory - something else? -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak@suse.cz , l.lunak@kde.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Monday February 15 2010 11:57:36 Lubos Lunak wrote:
On Saturday 13 of February 2010, Adrian Schröter wrote:
Am Freitag, 12. Februar 2010 16:40:36 schrieb Stephan Kleine:
On Friday February 12 2010 16:35:14 Lubos Lunak wrote:
I don't understand why we should solve this by having a separate
vendor and not e.g. repo priorities. What exactly is the purpose of having a different vendor? It's very likely that we either should not do this or do it for more subrepositories of KDE: .
Priorities are repository wide. So it weren't possible to use e.g. Amarok from K:K:P while sticking to the Ktorrent from K:K:F:D.
Because vendors are set for every package the above usecase weren't a problem with different vendors.
Vendors give the user the chance to decide which version of a package to pick.
Also zypper/yast are showing when a package changes the Vendor. So the user has a chance to decide on his own.
Vendors are about trust in the end. For example a user might be fine to use $unimportant_small_application from Playground, but he may not be fine to use kdebase from there.
Ok, whatever, but then this is not just about Playground. I may not want to use something from Community, or from Factory, or from UNSTABLE or maybe somewhere else. So which all repos should have their own vendor?
- Playground - Community - UNSTABLE - Factory - something else?
[UN]STABLE & Factory are done by Novell folks and there's no reason to mix them (enabling 2 of them simply makes no sense) so they don't "need" a different vendor. Further them having different vendors would make it harder (cause of the vendor stickiness / explicit change) if one switches e.g. from STABLE to Factory. Playground needs a different vendor for the reasons explained above and Community is run by the community (as in different people than [UN]STABLE & Factory) so one could argue that the "trust level" isn't the same and therefore it should have a different vendor too. So I would vote for [UN]STABLE & Factory sticking with the current vendor and Community and Playground each getting their unique vendor. regards, Stephan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On 15/02/10 22:09, Stephan Kleine wrote:
On Monday February 15 2010 11:57:36 Lubos Lunak wrote:
On Saturday 13 of February 2010, Adrian Schröter wrote:
Am Freitag, 12. Februar 2010 16:40:36 schrieb Stephan Kleine:
On Friday February 12 2010 16:35:14 Lubos Lunak wrote:
I don't understand why we should solve this by having a separate
vendor and not e.g. repo priorities. What exactly is the purpose of having a different vendor? It's very likely that we either should not do this or do it for more subrepositories of KDE: .
Priorities are repository wide. So it weren't possible to use e.g. Amarok from K:K:P while sticking to the Ktorrent from K:K:F:D.
Because vendors are set for every package the above usecase weren't a problem with different vendors.
Vendors give the user the chance to decide which version of a package to pick.
Also zypper/yast are showing when a package changes the Vendor. So the user has a chance to decide on his own.
Vendors are about trust in the end. For example a user might be fine to use $unimportant_small_application from Playground, but he may not be fine to use kdebase from there.
Ok, whatever, but then this is not just about Playground. I may not want to use something from Community, or from Factory, or from UNSTABLE or maybe somewhere else. So which all repos should have their own vendor?
- Playground - Community - UNSTABLE - Factory - something else?
[UN]STABLE & Factory are done by Novell folks and there's no reason to mix them (enabling 2 of them simply makes no sense) so they don't "need" a different vendor. Further them having different vendors would make it harder (cause of the vendor stickiness / explicit change) if one switches e.g. from STABLE to Factory.
Playground needs a different vendor for the reasons explained above and Community is run by the community (as in different people than [UN]STABLE & Factory) so one could argue that the "trust level" isn't the same and therefore it should have a different vendor too.
So I would vote for [UN]STABLE & Factory sticking with the current vendor and Community and Playground each getting their unique vendor.
regards, Stephan
I guess for PLAYGROUND you are referring to this latest list; [DIR] Parent Directory http://download.opensuse.org/repositories/KDE:/KDE4:/ - [DIR] SLE_11/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/SLE_11/ 26-Dec-2009 23:26 - [DIR] openSUSE_11.0/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Dec-2009 09:49 - [DIR] openSUSE_11.0_KDE4_Factory_Desktop/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:21 - [DIR] openSUSE_11.0_KDE4_STABLE_Desktop/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 14-Feb-2010 10:39 - [DIR] openSUSE_11.0_KDE_43/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:22 - [DIR] openSUSE_11.1/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 26-Dec-2009 23:01 - [DIR] openSUSE_11.1_KDE4_Factory_Desktop/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:13 - [DIR] openSUSE_11.1_KDE4_STABLE_Desktop/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:14 - [DIR] openSUSE_11.1_KDE4_UNSTABLE_Desktop/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:21 - [DIR] openSUSE_11.1_KDE_43/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:13 - [DIR] openSUSE_11.2/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:13 - [DIR] openSUSE_11.2_KDE4_Factory_Desktop/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:34 - [DIR] openSUSE_11.2_KDE4_UNSTABLE_Desktop/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:14 - [DIR] openSUSE_11.2_KDE_43/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_11.... 16-Feb-2010 01:11 - [DIR] openSUSE_Factory/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_Fac... 16-Feb-2010 01:28 - [DIR] openSUSE_Factory_KDE4_UNSTABLE_Desktop/ http://download.opensuse.org/repositories/KDE:/KDE4:/Playground/openSUSE_Fac... 16-Feb-2010 01:13 - under Index of /repositories/KDE:/KDE4:/Playground There is another, similar list under the Community directory. All fine (said with tongue in cheek), but my question is: Could you, or someone, * please* tell us who is in *charge*, who is *in* *control*, who is *overseeing*, who is the *management team* of the repositories, their names, their direction, their contents and co-ordinating their contents? This is a genuine question, so don't come up with the '"you're a troll"' crap. Who *IS* running the show? Novell? SuSE? KDE? "Community" - but who in the "Community"? Redmond? Who? BC -- The calendar's days are numbered! -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Tuesday February 16 2010 10:37:12 Basil Chupin wrote <snip />
All fine (said with tongue in cheek), but my question is:
Could you, or someone, * please* tell us who is in *charge*, who is *in* *control*, who is *overseeing*, who is the *management team* of the repositories, their names, their direction, their contents and co-ordinating their contents?
If you want to know who exactly is listed as maintainer for which repository just look it up yourself on build.opensuse.org. Basically everyone who wants gets access to Community & Playground with Playground providing alpha & beta versions and Community providing programs that aren't included in the official distro. [UN]STABLE & Factory contain all KDE packages that are included in the official openSUSE distribution and is currently maintained by paid Novell employees. Same for Backports which provides backports of newer programs contained in the official distribution build for older releases.
This is a genuine question, so don't come up with the '"you're a troll"' crap.
Who *IS* running the show?
Novell? SuSE? KDE? "Community" - but who in the "Community"? Redmond? Who?
Considering your last sentence it's somehow hard to spare you the trolling part but who's surprised here ...
BC
-- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Tuesday, February 16, 2010, Stephan Kleine wrote:
If you want to know who exactly is listed as maintainer for which repository just look it up yourself on build.opensuse.org.
Basically everyone who wants gets access to Community & Playground with Playground providing alpha & beta versions and Community providing programs that aren't included in the official distro.
I'm a OBS user. In 'home:plcl:kde4' [1] project I'm packaging my own MIDI related applications: KMid2, KMetronome, KMidimon and VMPK. I've asked some time ago in this same list [2] to join Community & Playground for my projects. Will Stephenson answered with a welcome message and some valuable technical suggestions (thanks!), but I'm still waiting for somebody to tell me yes/no, or what to do in order to have my applications available in the Community & Playground repositories. Regards, Pedro [1] https://build.opensuse.org/project/show?project=home%3Aplcl%3Akde4 [2] http://thread.gmane.org/gmane.linux.suse.kde/9754 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Tuesday February 16 2010 12:52:57 Pedro Lopez-Cabanillas wrote:
On Tuesday, February 16, 2010, Stephan Kleine wrote:
If you want to know who exactly is listed as maintainer for which repository just look it up yourself on build.opensuse.org.
Basically everyone who wants gets access to Community & Playground with Playground providing alpha & beta versions and Community providing programs that aren't included in the official distro.
I'm a OBS user. In 'home:plcl:kde4' [1] project I'm packaging my own MIDI related applications: KMid2, KMetronome, KMidimon and VMPK.
I've asked some time ago in this same list [2] to join Community & Playground for my projects. Will Stephenson answered with a welcome message and some valuable technical suggestions (thanks!), but I'm still waiting for somebody to tell me yes/no, or what to do in order to have my applications available in the Community & Playground repositories.
Regards, Pedro
[1] https://build.opensuse.org/project/show?project=home%3Aplcl%3Akde4 [2] http://thread.gmane.org/gmane.linux.suse.kde/9754
I added you to Community & Playground so feel free to copy your packages over. One thing though I found with your packages is the package-with-huge- translation in kmetronome which is very easy to fix: In the header of the spec: "%lang_package" In %install: "%find_lang %{name}" (as you already have it) and at the end of the spec "%files lang -f %{name}.lang". Voila, you know have a separate -lang package ;) hth Stephan -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Tuesday, February 16, 2010, Stephan Kleine wrote:
I added you to Community & Playground so feel free to copy your packages over.
Thanks!
One thing though I found with your packages is the package-with-huge- translation in kmetronome which is very easy to fix:
In the header of the spec: "%lang_package"
In %install: "%find_lang %{name}" (as you already have it)
and at the end of the spec "%files lang -f %{name}.lang".
Voila, you know have a separate -lang package ;)
Thanks again. I will create separate -lang packages, but this warning is a bit bogus, IMO. KMetronome has only three GUI translations (Spanish, French and Czech) totalizing about 20K unpacked, far from the 56% of the package reported by RPMLINT. On the other hand, kmid2 has 11 GUI translations and 5 documentation languages and it is not reported ;-) Regards, Pedro -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Monday 15 of February 2010, Stephan Kleine wrote:
So I would vote for [UN]STABLE & Factory sticking with the current vendor and Community and Playground each getting their unique vendor.
Ok. I've created new keys for KDE:Community, KDE:KDE4:Community and KDE:KDE4:Playground. -- Lubos Lunak openSUSE Boosters team, KDE developer l.lunak@suse.cz , l.lunak@kde.org -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
On Thursday 11 February 2010 23:15:59 Stephan Kleine wrote:
Hi guys.
Could you please be so kind to use a different vendor for the KDE:KDE4:Playground repo than for the stable ones?
Reasoning is that with K:K:P added I get updated to beta versions from e.g. Amarok & Ktorrent while being unable to prevent that somehow which currently forces me to constantly enable & disable the repo which is a pita.
This seems reasonable to me, because KDE:KDE4:Playground (and KDE:KDE4:Community, for that matter) have different maintainers to the KDE:KDE4:*:Desktop repos, so people may take policy decisions based on vendor. Will -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kde+help@opensuse.org
participants (7)
-
Adrian Schröter -
Basil Chupin -
Christian Trippe -
Lubos Lunak -
Pedro Lopez-Cabanillas -
Stephan Kleine -
Will Stephenson