I've been finishing the branding work for 11.3 this week, and have been
documenting how to do it as I go. The first draft is attached. Comments? If
I was hit by a bus tomorrow, could you do openSUSE 11.4 branding? (Lubos
doesn't need to answer that ;)).
Will
--
Will Stephenson, KDE Developer, openSUSE Boosters Team
SUSE LINUX Products GmbH - Nürnberg - AG Nürnberg - HRB 16746 - GF: Markus Rex
Hello Mates,
i have some Questions about that Repository.
1.) I have 3 Packages (assuma, skrooge and kpassgen). Have
i full control in this package? So i can use osc co and ci, or must i use submitrequest?
2.) I've seen that the
publish is diabled. Can i enable this?
Have a nice day...
--
Sincerely yours
Sascha Manns
open-slx GmbH
openSUSE
Community & Support Agent
openSUSE Marketing Team
Blog: http://saigkill.wordpress.com
Web: http://www.open-slx.de
(openSUSE Box Support German)
Web: http://www.open-slx.com (openSUSE Box Support English)
Hi guys,
you either receive this email because you are listed as maintainer for
KDE:KDE4:Community or are subscribed to opensuse-kde (and I couldn't be
bothered to sort out the emails so my apologies if I'm telling you the
obvious).
Point being: KDE:KDE4:Community will get nuked soon and the new place is
KDE:Extra
See recent threads on opensuse-kde or http://old-en.opensuse.org/KDE/Extra_Repository for details.
Therefore please be so kind to review the packages you are interested in and
submit them to KDE:Extra. Also please get rid of the "kde4-" prefix and add
some proper Provides and Obsoletes in the specs header. For any question just
ask on the opensuse-kde or opensuse-buildservice MLs or IRC.
Following the new policy you either have to use SRs to submit your packages
and normally will get only maintainership for your single package. If you
would like to become repo wide maintainer of KDE:Extra please apply on the
opensuse-kde ML and read the above wiki link before to make sure you
understand what that would mean (as in responsibilities).
Also please make sure to remove any transferred packages from
KDE:KDE4:Community since this makes it much easier to see what already got
transferred.
Thanks a lot & best regards,
Stephan
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hi all,
I have upgraded my laptop to 11.3 from 11.1 and everything works fine except
hibernate and suspend options in the kicker menu only locks the screen and not
do suspend/hibernate. If i run pm-hibernate or pm-suspend then everything
works correctly and restarts correctly.
Any ideas?
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hi,
it would be nice if you could enable again to have different vendors for
KDE:Extra and KDE:Unstable:Playground then the one for the main repos like
KDE:Distro:*
Christian
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
As that the renaming of the openSUSE KDE related repositories has been
completed, it is time to introduce the second step for the KDE:Unstable:SC
repository.
The intention is to minimize this particular repository to the pure KDE SC
weekly snapshots from trunk and the required libraries/applications for
building and running the Unstable desktop.
All other applications (e.g. Amarok, Konversation, etc) will be moved out to
the other repositories. With the new snapshot 4.5.62 a couple of them have
already been moved to KDE:Unstable:Playground. These are the packages for
Amarok, Choqok, Konversation and Rekonq. I also updated these applications
to their respective latest svn/git snapshots.
Regards
Raymond
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
On Saturday 31 July 2010 17:48:38 todd rme wrote:
> I stated this before, but this really concerns me. When we get around
> to beta/RC stage of KDE SC, people will be able to use a mostly stable
> KDE SC, but they will be forced to use it with perhaps the pre-alpha
> level versions of popular programs like amarok that will be found in
> the playground repository. This could very well be the case for any
> KDE-based software that does not synchronize with KDE SC release
> cycle. I think people using the unstable repository need to have a
> way to install stable versions of KDE software that is not part of KDE
> SC, or there will be a very serious risk of making the Unstable
> repository nearly much unusable in practice (since no remotely stable
> version of key software will necessarily be available).
Dear Todd,
I believe that with the Beta cycle for KDE 4.5 it was the frst time that
people switched over to the Unstable repository to get their hands on KDE 4.5.
What must not be forgotten is that the Unstable Repository doesn't have most
of the openSUSE patches in place, nor does it come with any warranty.
Since already a couple of months we had the situation where the Amarok and
Konversation packages in this repository were updated from trunk in the same
frequency as the KDE desktop itself.
The intention for the Unstable repository is that it would be co-installable
besided the normal supported KDE desktop (KDE:Distro:Factory). This in the
same manor as we had with KDE3 and KDE4.
Regards
Raymond
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hello Mates,
just a question. In the kde-extragear List gdebure says, that skrooge in
the last version needs qca-ossl as runtime depency.
Has anyone this build in the OBS, or planned?
Have a nice weekend.
--
Sincerely yours
Sascha Manns
open-slx GmbH
openSUSE Community & Support Agent
openSUSE Marketing Team
Blog: http://saigkill.wordpress.com
Web: http://www.open-slx.de (openSUSE Box Support German)
Web: http://www.open-slx.com (openSUSE Box Support English)
After management found some loose change down the back of the sofa at the end
of the quarter I spent it on some Bluetooth kit including a headset to test
the new Bluedevil KDE Bluetooth UI. This morning I got the headset working
with KDE SC 4.5.
I would like to discuss testing PulseAudio for KDE in
openSUSE 11.4.
I hope that by then our crash test dummies who are already
using PA will have run over all the major, frequent bugs in implementation
and deployment for us.
The advantage over plain ALSA that appeals to me is
allowing the user to do some useful configuration of her audio environment
with UI tools, as this covers the (for example) Bluetooth case of
configuring music/effects to come out of the speakers while VOIP calls are
handled by a headset. I guess you can do that with ALSA but it will
probably be a static setup and there is no KDE UI for it.
Since KDE SC
4.5 there is a nice UI for configuring PulseAudio's Phonon backend, and KMix
supports dynamic PA mixers and application audio streams. When 4.6 is
released there will be a speaker setup System Settings module that can let
you select audio processing depending on your speaker setup and configure
audio profiles for devices.
The other reason for embracing PA is that
it's not going away from the distribution. At the moment (11.3) we have
kept the zombies away from our sound cards on the KDE CD by removing
anything that uses it, but this is fragile - most users will soon install
other software that pulls in PA as a dependency.
By testing out PA now we
can help fix bugs in the KDE infrastructure and discover problems with the
rest of openSUSE's KDE multimedia stack (eg see how Phonon VLC works with
PA.
FWIW, the steps I had to take to get the headset working with
KDE:Distro:Factory on 11.3 are:
(steps we would preconfigure OOTB for
11.4)
* install pulseaudio, pulseaudio-module-bluetooth and
pulseaudio-module-x11
* register KDE:Unstable:Playground repo
* install
bluedevil and start it with Service Manager (or relogin)
* uninstall
kbluetooth (not necessary but removes confusion due to 2 bluetooth icons)
*
start pulseaudio manually (or relogin)
* execute start-bluetooth-x11 and
start-bluetooth-kde
* from the Bluetooth system tray, Manage Devices...
*
Put the headset into pairing mode
* Add Device and run through the wizard
with default settings.
* Click 'trust' in the Bluetooth Device Manager.
*
restart kmix (or relogin)
* Play some music
* In kmix, open the mixer window
and go to playback streams, right click the eg amarok stream and select
'Move' to the headset device. Make sure the stream and the headset playback
device are not muted.
The last step won't be necessary once we rebuild
kdebase4-runtime with PulseAudio support, since then the Phonon KCM allows
phonon sound categories to be routed to specific devices.
Thoughts?
More
info and debugging tips at http://pulseaudio.org/wiki/KDE
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(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hello Mates,
i would like to invite you to publish your weekly review in our Weekly
News. Maybe you have seen, that we have a special place for team reports
there. You can send news, suggestions and other stuff to: own-
submit(a)opensuse.org.
Thanks a löt for your work, :-)
--
Sincerely yours
Sascha Manns
open-slx GmbH
openSUSE Community & Support Agent
openSUSE Marketing Team
Blog: http://saigkill.wordpress.com
Web: http://www.open-slx.de (openSUSE Box Support German)
Web: http://www.open-slx.com (openSUSE Box Support English)