Hello,
in OBS in home:llunak:ksuseinstall there are packages branched from
KDE:KDE4:Factory:Desktop that have one experimental feature added: When a
needed package is not installed, the user is offered its installation.
Currently there is support for debuginfo packages, applications that can open
a specific file type if none is installed and multimedia codecs for Amarok.
The plan is that this feature makes it into 11.3, so please test and provide
feedback.
The things I'm especially interested in:
- the UI and the workflow could quite possibly be improved (currently it uses
Yast modules to save me a lot of work, and it's also done this way because of
a certain catch mentioned below). So, imagine you are Joe User the Clueless
who's just installed 11.3 and think about how this would or would not work
and how it could be improved.
The catch here is that this is not only a technical problem but also a
legal :(. This can quite easily help with the problem of installing packages
that cannot be shipped as a part of openSUSE because of various stupid patent
stuff etc. The problem is that we should not even encourage too much usage of
such packages. Don't ask what that means exactly, because I don't know, and
probably not even lawyers know for sure, but something like "MP3 support is
missing, press Yes to install it from Packman" is simply very unlikely to
make it past our lawyers. I think the guideline could be that the user has to
know it's an extra and that it's not part of openSUSE, and thus has to make
at least some effort, not just confirm a dialog. There is a reason why adding
community repositories in Yast fetches a list of those from a 3rd party site
and knows nothing else than the URL of that list. Yes, this all sucks.
- there could be more places where this could help a lot, either by saving the
default installation size by not installing packages that most users wouldn't
use, or by handling something where such on-demand installation would be
helpful to many users. From 11.2 the Nepomuk/Strigi config module comes to
mind - we had it disabled by default and some parts were not installed, so
enabling it required not only flipping the checkbox but also installing
something. I am not going to patch every single place in KDE where an
optional package could be possibly missing, but it shouldn't be difficult to
handle some mores places where it makes a difference, if you know such cases.
--
Lubos Lunak
openSUSE Boosters team, KDE developer
l.lunak(a)suse.cz , l.lunak(a)kde.org
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hi there.
I'd like to inform you that K3b received a new bugfix release:
http://sourceforge.net/projects/k3b/files/
Changelog:
* In some cases medium doesn't get accepted for multisession burning (230742)
* Data files in VCD ripping view are not listed
* Show "Modify Permissions" button in System Problem Dialog only when it
makes sense (230706)
* Crash after "Cancel" was clicked while adding audio files to AudioCD
project (231348)
* Error window at the start when a place on the left pane is not accessible
(230194)
* Incorrect minimum size of welcome widget (231939)
* Hangs while ripping AudioCD with data tracks (231174)
* Crash when auto-removing non-existing files from a project before the
burning (236005)
* Empty Blu-ray medium not detected properly (236069)
* eMovix project cannot be burned (236823)
* M3U playlist not read properly (237654)
* K3b overwrites iso ignoring user choice on dvd copy with option "only
create image" checked (185251)
* Compilation fails with FFmpeg version SVN-r23001 (236036)
* Crash when waiting for reload the medium
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hi, my package kde4 community kid3 is failing in all kde4 unstable
builds with a doc related (kdelibs4-doc) problem, is there something
happening in unstable or is this something that needs to be fixed by me
before it spreads to stable builds.
Thanks
Dave P
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Here are the minutes for the KDE Team meeting on 2010/05/27
See http://en.opensuse.org/KDE/Meetings/ for futher details.
== Old action items ==
* lunak,wstephenson document how-to-maintain Extra
** not done yet
== ksuseinstall ==
* http://help.opensuse.org/ksuseinstall
* will be used in the ksuseinstall dialog to guide people
* AI: wstephenson, javier_ write the ksuseinstall text
== The most annoying 11.3 bugs and M7 status ==
* release nearing, so bug triage is on, help is very welcome
* P2 anything that needs to be fixed before release
* P1 anything really broken
* AI: javier_ announce and run a bug triage
* AI: llunak pointers for javier_
* AI: wstephenson make a contact to KDE bugsquad for javier_
* AI: cb400f run tests for kupdateapplet, ping opensuse-maintainance
== Making the meetings more interesting/well attended ==
* cb400f / rabauke suggest better visibility and interesting topics
* another timeslot is evaluated, will be done on -kde list
* wstephenson suggests topic focused meetings
* suitable tasks to hook new contributors are evaluated
* group hugs are shared because the meeting is packed with people!
* make opensuse more visible as good upstream partner
* wstephenson asks to please use proper blog tags not to swamp planetkde with
opensuse specific posts
* AI: llunak add additional meeting reminder mail more days in advance
* AI: llunak update meeting howto to highlight people on IRC about meeting
starting (or something similar)
* AI: everybody blog more about opensuse kde work, also about other (quieter)
peoples work, add blog to the planets
* AI: rabauke start blogging regularly about happenings in the project
* AI: everybody push kde news to saigkill for the openSUSE news
* AI: wstephenson see if rpmlint warnings can be hung on a lime tree for easy
plucking
* AI: wstephenson mail list about meeting times
== bugs that wstephenson might not get to that need to be done ==
* currently akonadi starts with kde and produces failure messages
* https://bugzilla.novell.com/show_bug.cgi?id=591483
* wstephenson targets on demand start of akonadi
* device notifier not working always, plasma team looking into it
* https://bugzilla.novell.com/597162
* AI: wstephenson summarise big bugs to list
== Repository reorganisation update ==
* still no consensus on details
* llunak made an overview and voting page on the wiki
* biggest issue is the placement and intention of UNSTABLE
* http://en.opensuse.org/KDE/RepositoryRenaming
* AI: everybody comment and vote on repositories
== Q&A, Misc ==
* chitchat about a splitted kontact and rpms 'suggests' tag
* general praise about the community, and certain people who are the quiet
heroes of the opensuse-kde team
== Action items ==
* AI: wstephenson, javier_ write the ksuseinstall text
* AI: javier_ announce and run a bug triage
* AI: llunak pointers for javier_
* AI: wstephenson make a contact to KDE bugsquad for javier_
* AI: cb400f run tests for kupdateapplet, ping opensuse-maintainance
* AI: llunak add additional meeting reminder mail more days in advance
* AI: llunak update meeting howto to highlight people on IRC about meeting
starting (or something similar)
* AI: everybody blog more about opensuse kde work, also about other (quieter)
peoples work
* AI: rabauke start blogging regularly about happenings in the project
* AI: everybody push kde news to saigkill for the openSUSE news
* AI: wstephenson see if rpmlint warnings can be hung on a lime tree for easy
plucking
* AI: wstephenson mail list about meeting times
* AI: wstephenson summarise big bugs to list
* AI: everybody comment and vote on repositories
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hi, I've no problem finding the kde3 api documentation online or locally
but http://api.kde.org/ refuses connections and I can't find a package
containing the kde4 api docs anywhere even in the help center and
kdevelop3s google search turns up links but they're all to api.kde.org.
Regards
Dave P
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hello,
I have the AI from the last meeting to sum up the new structure and naming
here before we do a poll about the choices, so here it goes. According to the
discussion the repositories should be reorganized this way, with the
following names and purpose:
(note: KKFD = KDE:KDE4:Factory:Desktop, o:F = openSUSE:Factory)
- backports repository - name KDE:Backports, it contains latest versions of
KDE applications that are usable of any supported openSUSE release and do not
require newer KDE platform. In other words, all applications from the factory
development repo (current KKFD) but built against the distributions instead
of against KKFD. This repository is offered in repositories list in YaST.
Technically, this repo will only contain links to openSUSE:Factory for the
packages. Maintainers of the repository shouldn't need to do more than
enable/disable build and 'osc linkrev' to update to newer versions (the links
will point to specific revisions of o:F packages to avoid beta packages
appearing in KDE:Backports when they get submitted to o:F).
- unstable repository - name KDE:UNSTABLE, currently
KDE:KDE4:UNSTABLE:Desktop. Basically, SVN upstream snapshots, that's it.
- development repository - current KDE:KDE4:Factory:Desktop, suggested name
KDE:Distribution:Factory or others (see below). This repository contains all
packages maintained by the KDE team that are in o:F. Note that KDE team does
not mean just Will and me.
- stable repository - current KDE:KDE4:STABLE:Desktop, suggested name
KDE:Distribution:STABLE or others (see below). Contains all packages
maintained by the KDE team that are in the latest stable openSUSE release. In
other words, when there is a new distribution release, contents of the above
(~KKFD) repo get copied here and the repo is used for preparing online
updates and similar.
- additional packages repository - suggested name KDE:Extra or others (see
below), for packages which are not in o:F (like current KDE:KDE4:Community
but hopefully without the random state of things). This repository is offered
in repositories list in YaST. Only stable releases of packages are allowed
here, or a reasonably stable beta release if an official stable release is
not available. Repository-wide maintaners are only people who maintain the
repository as a whole. People willing to contribute packages will do submit
requests that will be reviewed by maintainers, when trusted enough they get
maintainership only for their package(s). Current KDE:KDE4:Community will be
eventually deleted after packages are moved to this new repository (not
necessarily all of them).
- playground repository - name KDE:Playground, contains any KDE packages
without any guarantee (alpha versions, whatever). Not as strongly reviewed
and maintained as the other repositories (I don't know what the best way to
handle this in practice would be, depends also on manpower, but I think there
still should be only few repo-wide maintainers who would give package
maintainership to others).
That's all as far as the reorganization goes. This will be done before 11.3
is released, we will try to keep links for backwards compatibility for some
(unknown time). Please review and comment/fix/etc.
Also please raise your hand again if you'd be willing to do a repository
maintainer for any of these. There were several people for KDE:Backports
(where it should be pretty simple) and KDE:Extra stepping up during the
meeting, so I'd like just to have a written overview here.
Naming: Since we are already going to do repository renaming to e.g.
remove 'Community' from the name of the repository with additional packages
to avoid suggesting that it is the only repository where community can
contribute, we decided to do it all at once and also do other renaming to fix
other problems with repository naming. For example, in
KDE:KDE4:Factory:Desktop the 'KDE4' is superfluous and 'Desktop' is just a
part of the contents, and we could use a better word than 'Factory' to
suggest that it is packages that will be in the distribution.
Therefore, here is a list of names that were proposed during the meeting. For
some the consensus seemed clear, so there is just one, but feel free to
suggest other options there too.
- backports:
- KDE:Backports
- unstable:
- KDE:UNSTABLE
- KDE:Unstable
- development:
- KDE:Distribution:Factory
- KDE:Distro:Factory
- KDE:Base:Factory
- (KDE:SC:Factory is not listed as the contents are not just KDE Software
Compilation)
- ?
- stable:
- KDE:Distribution:STABLE
- replace 'Distribution' with all choices above for it, and STABLE can again
get different capitalization
- ?
- additional:
- KDE:Extra
- KDE:Contrib (this is not very liked, as it has similar implications
like 'Community')
- playground:
- KDE:Playground
After feedback (or if there is none :) ), I will create polls for the
possibilities and best names will be chosen. After that, we will create the
new structure, setup maintainers for the repos and start moving contents.
--
Lubos Lunak
openSUSE Boosters team, KDE developer
l.lunak(a)suse.cz , l.lunak(a)kde.org
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
The next openSUSE KDE Team meeting will be held tomorrow,
Thursday 27th May, at 16:00 UTC.
The current list of scheduled topics is:
* http://help.opensuse.org/ksuseinstall
* most annoying 11.3 bugs
* making the meetings more interesting/well attended
* default Akonadi startup/usage
* repository reorganization
* old action items
* status report
* Q&A, misc
Further items are welcome; please add them http://en.opensuse.org/KDE/Meetings
Please use
http://www.timeanddate.com/worldclock/fixedtime.html?day=27&month=5&year=20…
to get the time of the meeting in your time zone.
The meeting will happen in #opensuse-kde IRC channel on irc.freenode.net
You are welcome to join and participate!
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Can anyone tell me what this means and do I need nbcluster enabled?
Cannot find way to enable it.
100525 7:31:39 [Note] Plugin 'ndbcluster' is disabled.
100525 7:31:39 InnoDB: Started; log sequence number 0 17400584
100525 7:31:39 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.36-log' socket:
'/home/finemanruss/.local/share/akonadi/db_misc/mysql.socket' port:
0 SUSE MySQL RPM
Thanks!
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
Hi,
Burkhard Lück fixed the compile/install failure:
http://websvn.kde.org/?view=revision&revision=1130001
Johannes
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org
i thought some here might find it interesting that some folks decided to
continue maintaining KDE 3.5.
the source can be found at <http://websvn.kde.org/branches/>, ubuntu
packages here: <https://launchpad.net/~kde3-
maintainers/+archive/trinity-svn-nightly/+packages> i don't know if
packages for other distros are planned; their roadmap isn't very
complete yet:
"This page will (eventually) detail the direction the Trinity project is
heading in. For now, we are busy keeping the efficient KDE3 interface
alive and up-to-date, as well as patching security holes and adding
advanced new features!"
apparently they're thinking to improve on the present 3.5.10 version,
and i thought people who have strong opinions what should or shouldn't
have been done with KDE 3.5 might want to get involved during the
beginning stage of such a project.
--
phani.
--
To unsubscribe, e-mail: opensuse-kde+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-kde+help(a)opensuse.org