[opensuse-kde] Can the KDE:Unstable:SC packages be updated to version 4.8.97
Hello, Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97, source packages listed at [2] Relese notice at [3]. Thanks Glenn [1]https://build.opensuse.org/project/packages?project=KDE%3AUnstable%3ASC [2]http://download.kde.org/unstable/4.8.97/src/ [3]http://kde.org/announcements/announce-4.9-rc2.php -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Dienstag, 17. Juli 2012, 21:02:34 schrieb doiggl@velocitynet.com.au:
Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97, source packages listed at [2] Relese notice at [3].
The maintainer (not paid by openSUSE) is on holiday and nobody else seems to bother updating the repo. So unless you feel like updating the repo with the new sources etc. you will have to wait until somebody else does so. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tue, Jul 17, 2012 at 1:46 PM, Sven Burmeister <sven.burmeister@gmx.net> wrote:
Am Dienstag, 17. Juli 2012, 21:02:34 schrieb doiggl@velocitynet.com.au:
Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97, source packages listed at [2] Relese notice at [3].
The maintainer (not paid by openSUSE) is on holiday and nobody else seems to bother updating the repo. So unless you feel like updating the repo with the new sources etc. you will have to wait until somebody else does so.
Sven
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tue, 17 Jul 2012 17:41:01 +0200, Markus <kamikazow@gmx.de> wrote:
Am Dienstag 17 Juli 2012, 13:49:06 schrieb todd rme:
Might it be time now to setup a KDE:Release:49 repo?
Was about to ask that as well ;-)
Hello, Sounds like a good idea Could someone clone/copy KDE:Unstable:SC <packagename> to KDE:Release:49 <packagename> And the 4.8.97 files can be added in there. I have no permission to do that though. Cheers Glenn -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tue, Jul 17, 2012 at 1:46 PM, Sven Burmeister <sven.burmeister@gmx.net> wrote:
Am Dienstag, 17. Juli 2012, 21:02:34 schrieb doiggl@velocitynet.com.au:
Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97,
On Tue, 17 Jul 2012 13:49:06 +0200, todd rme <toddrme2178@gmail.com> wrote: source
packages listed at [2] Relese notice at [3].
The maintainer (not paid by openSUSE) is on holiday and nobody else seems to bother updating the repo. So unless you feel like updating the repo with the new sources etc. you will have to wait until somebody else does so.
Sven
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
-Todd
Hello, Thanks Todd Can the following be done. - Since this is unstable kde , could KDE:Unstable:SC <packagename> be used, with the 4.8.97 file(s) added in see list [1] below. - I have a copy of the kde 4.8.97x source files. - I could upload the new source file to the kde packagename, need permission to do so, a osc command file would be useful to add the new source file to the package. Need osc commands to do that, like the following: osc cd KDE:Unstable:SC<packagename> osc add <new-filename-4.8.97.tar.xz> osc commit next package - update spec file - replace 4.8.95 with 4.8.97 [1] source listing # ll total 731341 143248 Jul 11 13:09 analitza-4.8.97.tar.xz 153640 Jul 11 13:09 ark-4.8.97.tar.xz 54884 Jul 11 13:09 audiocd-kio-4.8.97.tar.xz 564716 Jul 11 13:09 blinken-4.8.97.tar.xz 264384 Jul 11 13:09 cantor-4.8.97.tar.xz 391804 Jul 11 13:09 dragon-4.8.97.tar.xz 20068 Jul 11 13:09 ffmpegthumbs-4.8.97.tar.xz 294092 Jul 11 13:09 filelight-4.8.97.tar.xz 2048528 Jul 11 13:09 gwenview-4.8.97.tar.xz 365612 Jul 11 13:09 jovie-4.8.97.tar.xz 440692 Jul 11 13:09 juk-4.8.97.tar.xz 20480 Jul 11 13:09 kaccessible-4.8.97.tar.xz 83432 Jul 11 13:09 kactivities-4.8.97.tar.xz 439148 Jul 11 13:09 kalgebra-4.8.97.tar.xz 3707820 Jul 11 13:09 kalzium-4.8.97.tar.xz 36648 Jul 11 13:09 kamera-4.8.97.tar.xz 1067600 Jul 11 13:10 kanagram-4.8.97.tar.xz 2144200 Jul 11 13:10 kate-4.8.97.tar.xz 905516 Jul 11 13:10 kbruch-4.8.97.tar.xz 87384 Jul 11 13:10 kcalc-4.8.97.tar.xz 85880 Jul 11 13:10 kcharselect-4.8.97.tar.xz 4308 Jul 11 13:10 kcolorchooser-4.8.97.tar.xz 16456568 Jul 11 13:22 kde-base-artwork-4.8.97.tar.xz 2488892 Jul 11 13:21 kde-baseapps-4.8.97.tar.xz 6346232 Jul 11 13:30 kde-runtime-4.8.97.tar.xz 77198752 Jul 11 13:37 kde-wallpapers-4.8.97.tar.xz 22358900 Jul 11 13:39 kde-workspace-4.8.97.tar.xz 1151904 Jul 11 13:10 kdeadmin-4.8.97.tar.xz 138023568 Jul 11 13:21 kdeartwork-4.8.97.tar.xz 56019648 Jul 11 13:27 kdegames-4.8.97.tar.xz 19500 Jul 11 13:27 kdegraphics-mobipocket-4.8.97.tar.xz 39996 Jul 11 13:27 kdegraphics-strigi-analyzer-4.8.97.tar.xz 41220 Jul 11 13:27 kdegraphics-thumbnailers-4.8.97.tar.xz 11712556 Jul 11 19:25 kdelibs-4.8.97.tar.xz 8947080 Jul 11 13:28 kdenetwork-4.8.97.tar.xz 14118516 Jul 11 13:29 kdepim-4.8.97.tar.xz 1116460 Jul 11 13:30 kdepim-runtime-4.8.97.tar.xz 2789600 Jul 11 19:14 kdepimlibs-4.8.97.tar.xz 1748912 Jul 11 13:30 kdeplasma-addons-4.8.97.tar.xz 5079616 Jul 12 00:01 kdesdk-4.8.97.tar.xz 377992 Jul 11 13:31 kdetoys-4.8.97.tar.xz 2571496 Jul 11 13:37 kdewebdev-4.8.97.tar.xz 155400 Jul 11 13:39 kdf-4.8.97.tar.xz 60584 Jul 11 13:39 kfloppy-4.8.97.tar.xz 26284 Jul 11 13:39 kgamma-4.8.97.tar.xz 6727236 Jul 11 13:40 kgeography-4.8.97.tar.xz 809024 Jul 11 13:40 kgpg-4.8.97.tar.xz 3772068 Jul 11 13:40 khangman-4.8.97.tar.xz 1511212 Jul 11 13:40 kig-4.8.97.tar.xz 937184 Jul 11 13:40 kimono-4.8.97.tar.xz 11744592 Jul 11 13:41 kiten-4.8.97.tar.xz 2652192 Jul 11 13:42 klettres-4.8.97.tar.xz 91772 Jul 11 13:42 kmag-4.8.97.tar.xz 300640 Jul 11 13:42 kmix-4.8.97.tar.xz 43000 Jul 11 13:42 kmousetool-4.8.97.tar.xz 319228 Jul 11 13:42 kmouth-4.8.97.tar.xz 677380 Jul 11 13:42 kmplot-4.8.97.tar.xz 1174536 Jul 11 13:42 kolourpaint-4.8.97.tar.xz 434584 Jul 11 13:42 konsole-4.8.97.tar.xz 160744 Jul 11 13:42 korundum-4.8.97.tar.xz 1079412 Jul 11 13:42 kremotecontrol-4.8.97.tar.xz 130776 Jul 11 13:42 kross-interpreters-4.8.97.tar.xz 133176 Jul 11 13:42 kruler-4.8.97.tar.xz 13136 Jul 11 13:42 ksaneplugin-4.8.97.tar.xz 93544 Jul 11 13:42 kscd-4.8.97.tar.xz 263000 Jul 11 13:42 ksnapshot-4.8.97.tar.xz 12324932 Jul 11 13:43 kstars-4.8.97.tar.xz 150284 Jul 11 13:43 ktimer-4.8.97.tar.xz 1713900 Jul 11 13:43 ktouch-4.8.97.tar.xz 212252 Jul 11 13:43 kturtle-4.8.97.tar.xz 281280 Jul 11 13:43 kwallet-4.8.97.tar.xz 1210332 Jul 11 13:43 kwordquiz-4.8.97.tar.xz 156856 Jul 11 13:43 libkcddb-4.8.97.tar.xz 75884 Jul 11 13:43 libkcompactdisc-4.8.97.tar.xz 267544 Jul 11 13:44 libkdcraw-4.8.97.tar.xz 209244 Jul 11 13:44 libkdeedu-4.8.97.tar.xz 133000 Jul 11 13:44 libkexiv2-4.8.97.tar.xz 75788 Jul 11 13:44 libkipi-4.8.97.tar.xz 80380 Jul 11 13:44 libksane-4.8.97.tar.xz 19840020 Jul 11 13:45 marble-4.8.97.tar.xz 27108 Jul 11 13:45 mplayerthumbs-4.8.97.tar.xz 372528 Jul 11 13:45 nepomuk-core-4.8.97.tar.xz 1370348 Jul 11 13:45 okular-4.8.97.tar.xz 276956964 Jul 11 14:07 oxygen-icons-4.8.97.tar.xz 1903988 Jul 11 14:07 pairs-4.8.97.tar.xz 8198628 Jul 11 14:08 parley-4.8.97.tar.xz 40184 Jul 11 14:08 perlkde-4.8.97.tar.xz 1813816 Jul 11 14:08 perlqt-4.8.97.tar.xz 35908 Jul 11 14:08 printer-applet-4.8.97.tar.xz 1991060 Jul 11 14:08 pykde4-4.8.97.tar.xz 530108 Jul 11 14:08 qtruby-4.8.97.tar.xz 510784 Jul 11 14:08 qyoto-4.8.97.tar.xz 1200364 Jul 11 14:08 rocs-4.8.97.tar.xz 146588 Jul 11 14:09 smokegen-4.8.97.tar.xz 37092 Jul 11 14:09 smokekde-4.8.97.tar.xz 30388 Jul 11 14:09 smokeqt-4.8.97.tar.xz 370868 Jul 11 14:09 step-4.8.97.tar.xz 383724 Jul 11 14:09 superkaramba-4.8.97.tar.xz 9012 Jul 11 14:09 svgpart-4.8.97.tar.xz 84036 Jul 11 14:09 sweeper-4.8.97.tar.xz -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tue, Jul 17, 2012 at 5:41 PM, <doiggl@velocitynet.com.au> wrote:
On Tue, Jul 17, 2012 at 1:46 PM, Sven Burmeister <sven.burmeister@gmx.net> wrote:
Am Dienstag, 17. Juli 2012, 21:02:34 schrieb doiggl@velocitynet.com.au:
Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97,
On Tue, 17 Jul 2012 13:49:06 +0200, todd rme <toddrme2178@gmail.com> wrote: source
packages listed at [2] Relese notice at [3].
The maintainer (not paid by openSUSE) is on holiday and nobody else seems to bother updating the repo. So unless you feel like updating the repo with the new sources etc. you will have to wait until somebody else does so.
Sven
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
-Todd
Hello, Thanks Todd Can the following be done. - Since this is unstable kde , could KDE:Unstable:SC <packagename> be used, with the 4.8.97 file(s) added in see list [1] below. - I have a copy of the kde 4.8.97x source files. - I could upload the new source file to the kde packagename, need permission to do so, a osc command file would be useful to add the new source file to the package. Need osc commands to do that, like the following:
osc cd KDE:Unstable:SC<packagename> osc add <new-filename-4.8.97.tar.xz> osc commit
next package
- update spec file - replace 4.8.95 with 4.8.97
KDE:Unstable:SC is intended for regular git snapshots. It is not the proper place for official betas or RCs. If you look now, you will see it does not contain 4.8.95. For example, it is using kde-runtime-4.8.95_20120629.tar.xz, which is a git snapshot done on June 29 2012. This is similar, but not identical, to 4.8.95. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 17 of July 2012 17:56:53 todd rme wrote:
On Tue, Jul 17, 2012 at 5:41 PM, <doiggl@velocitynet.com.au> wrote:
On Tue, 17 Jul 2012 13:49:06 +0200, todd rme <toddrme2178@gmail.com>
wrote:
On Tue, Jul 17, 2012 at 1:46 PM, Sven Burmeister
<sven.burmeister@gmx.net> wrote:
Am Dienstag, 17. Juli 2012, 21:02:34 schrieb doiggl@velocitynet.com.au:
Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97,
source
packages listed at [2] Relese notice at [3].
The maintainer (not paid by openSUSE) is on holiday and nobody else seems to bother updating the repo. So unless you feel like updating the repo
with
the new sources etc. you will have to wait until somebody else does so.
Sven
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
-Todd
Hello, Thanks Todd Can the following be done. - Since this is unstable kde , could KDE:Unstable:SC <packagename> be used, with the 4.8.97 file(s) added in see list [1] below. - I have a copy of the kde 4.8.97x source files. - I could upload the new source file to the kde packagename, need permission to do so, a osc command file would be useful to add the new source file to the package. Need osc commands to do that, like the following:
osc cd KDE:Unstable:SC<packagename> osc add <new-filename-4.8.97.tar.xz> osc commit
next package
- update spec file - replace 4.8.95 with 4.8.97
KDE:Unstable:SC is intended for regular git snapshots. It is not the proper place for official betas or RCs.
If you look now, you will see it does not contain 4.8.95. For example, it is using kde-runtime-4.8.95_20120629.tar.xz, which is a git snapshot done on June 29 2012. This is similar, but not identical, to 4.8.95.
-Todd
Also, at least KDEPIM is from master branch, don't know about other modules -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 17/07/12 21:49, todd rme wrote:
On Tue, Jul 17, 2012 at 1:46 PM, Sven Burmeister <sven.burmeister@gmx.net> wrote:
Am Dienstag, 17. Juli 2012, 21:02:34 schrieb doiggl@velocitynet.com.au:
Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97, source packages listed at [2] Relese notice at [3]. The maintainer (not paid by openSUSE) is on holiday and nobody else seems to bother updating the repo. So unless you feel like updating the repo with the new sources etc. you will have to wait until somebody else does so.
Sven Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
-Todd
Can someone, anyone, PLEASE take control of all of this, PLEASE?! This topic has been raised time and time again in the past: can someone stop the proliferation of the repositories for openSUSE? Even those people who maintain the wikis about openSUSE don't know what to write in the wikis they maintain to keep what is in them up-to-date. Why start yet another repo when surely all that is needed is to be added as another person who maintains in this particular repo? The current - and only person from what I have just read - is on holidays. OK, bad management practice regarding an important repo for a distro not to have a backup maintainer person. Fortunately this maintainer is only on holidays, but what would happen if he was run over by a bus? If you, Todd, are volunteering to also be a maintainer, and for which I admire you because I simply do not have the knowledge or ability to do so, then please don't ask for a new repo to be created - ask to added as one of the maintainer of this repo. Am I asking for something impossible because I am misinterpreting the situation and what is being written so far in this thread? If so, forgive me. BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.4.4.2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Mittwoch, 18. Juli 2012, 18:06:50 schrieb Basil Chupin:
This topic has been raised time and time again in the past: can someone stop the proliferation of the repositories for openSUSE? Even those people who maintain the wikis about openSUSE don't know what to write in the wikis they maintain to keep what is in them up-to-date.
Are you kidding? KRxy is the most straight-forward repo naming that exists.
Why start yet another repo when surely all that is needed is to be added as another person who maintains in this particular repo?
Because it is absolutely logical that 4.9 does not belong into a 4.8 repo. And it makes a lot of sense to let the user decide which KDE version to use. Having KRxy makes this easy. Having STABLE, Factory etc. not, because their name does not tell anything about the content.
The current - and only person from what I have just read - is on holidays.
OK, bad management practice regarding an important repo for a distro not to have a backup maintainer person.
The repo is unimportant by definition because it is only for unstable packages. This does not mean that Raymond is doing an unimportant job, quite in contrast, he is one of those contributing most to openSUSE. But whoever relies on unstable repos and runs into trouble if they are not updated for some weeks, is doing something wrong. Further, as others already pointed out, KUSC does contain snapshots, so it will never hold a x.y.z release and is simply not meant to be used for holding any KDE release to be used by "normal" users. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 18/07/12 18:50, Sven Burmeister wrote:
Am Mittwoch, 18. Juli 2012, 18:06:50 schrieb Basil Chupin:
This topic has been raised time and time again in the past: can someone stop the proliferation of the repositories for openSUSE? Even those people who maintain the wikis about openSUSE don't know what to write in the wikis they maintain to keep what is in them up-to-date. Are you kidding? KRxy is the most straight-forward repo naming that exists.
Why start yet another repo when surely all that is needed is to be added as another person who maintains in this particular repo? Because it is absolutely logical that 4.9 does not belong into a 4.8 repo. And it makes a lot of sense to let the user decide which KDE version to use. Having KRxy makes this easy. Having STABLE, Factory etc. not, because their name does not tell anything about the content.
The current - and only person from what I have just read - is on holidays.
OK, bad management practice regarding an important repo for a distro not to have a backup maintainer person. The repo is unimportant by definition because it is only for unstable packages. This does not mean that Raymond is doing an unimportant job, quite in contrast, he is one of those contributing most to openSUSE. But whoever relies on unstable repos and runs into trouble if they are not updated for some weeks, is doing something wrong. Thanks, Sven.
I cannot work out if you are being serious or being sarcastic in what you say above :-) . But if these are unstable repos then why are they even mentioned?
Further, as others already pointed out, KUSC does contain snapshots, so it will never hold a x.y.z release and is simply not meant to be used for holding any KDE release to be used by "normal" users.
I had better say that I don't consider that you are being sacrcastic otherwise someone like Patrick Shanahan will send down a bolt of lighting on me from Mount Olympus. But, to be honest, what the heck do "KUSC does not contain snapshots" and "will never hold a x.y.z release" and "[not] holding any KDE release to be used by "normal" users" mean in plain English language? :-(
Sven
BC -- Using openSUSE 12.2 x86_64 KDE 4.8.4 & kernel 3.4.4.2 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel Corsair "Vengeance" RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX550Ti 1GB DDR5 GPU -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri, Jul 20, 2012 at 12:20 PM, Basil Chupin <blchupin@iinet.net.au> wrote:
On 18/07/12 18:50, Sven Burmeister wrote:
Further, as others already pointed out, KUSC does contain snapshots, so it will never hold a x.y.z release and is simply not meant to be used for holding any KDE release to be used by "normal" users.
I had better say that I don't consider that you are being sacrcastic otherwise someone like Patrick Shanahan will send down a bolt of lighting on me from Mount Olympus. But, to be honest, what the heck do "KUSC does not contain snapshots" and "will never hold a x.y.z release" and "[not] holding any KDE release to be used by "normal" users" mean in plain English language? :-(
Sven
BC
You need to know something about how KDE is developed. In a simplified overview, KDE has something called "master", which is where unstable work is done. It has no real versions. Every so often, a versioned release is split off from that. Work goes into make sure that release is stable and works together. These are the x.y.z releases. Master is only close to stable for a brief time leading up the versioned releases, and even then using it is a bad idea because KDE devs usually split off the versioned releases fairly early (months before the official stable release) and cherry-pick changes from master to put into them. KDE:Unstable:SC has a roughly weekly snapshot of the work being done in master,. KDE:Release:xy has the versioned releases. To put it bluntly, we don't put the versioned releases in KDE:Unstable:SC because that is not what it is meant for. That is what the KDE:Release:xy repos are for. It is like asking "why don't we put KDE SC 4.9 rc2 in devel:languages:python", it is just the wrong repo for that. For ordinary users, you never want to use KDE:Unstable:SC. But for developers that are working on improving master, or advanced users who want to help test master, it is very useful. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 17 Jul 2012 13:49:06 todd rme wrote:
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Done, and you are maintainer. Please add qualified contributors too. Now start copying the KUSC packages in and replacing the git snapshots with upstream tarballs. I also recommend not trying to build vs every openSUSE release during the initial setup phase. WIll -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 19. Juli 2012, 12:37:25 schrieb Will Stephenson:
On Tuesday 17 Jul 2012 13:49:06 todd rme wrote:
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Done, and you are maintainer. Please add qualified contributors too. Now start copying the KUSC packages in and replacing the git snapshots with upstream tarballs.
Thanks!
I also recommend not trying to build vs every openSUSE release during the initial setup phase.
I would skip 11.4 altogether since its eol is close. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thu, Jul 19, 2012 at 12:37 PM, Will Stephenson <wstephenson@suse.de> wrote:
On Tuesday 17 Jul 2012 13:49:06 todd rme wrote:
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Done, and you are maintainer.
Great! Thanks!
Please add qualified contributors too.
How do I decide who is qualified? I am not trying to be sarcastic here, I have done a lot of work making packages, but I have no experience with those sorts of administrative decisions. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thursday, July 19, 2012 14:38:47 todd rme wrote:
On Thu, Jul 19, 2012 at 12:37 PM, Will Stephenson <wstephenson@suse.de> wrote:
On Tuesday 17 Jul 2012 13:49:06 todd rme wrote:
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Done, and you are maintainer.
Great! Thanks!
Please add qualified contributors too.
How do I decide who is qualified?
I am not trying to be sarcastic here, I have done a lot of work making packages, but I have no experience with those sorts of administrative decisions.
-Todd
Hi Todd, Please validate also the patches that are in KDF if they should be there for KR49 as well. I have tried my best to keep the patches in KUSC as up to date as possible, but didn't track any new patches that were pushed into KDF. Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thu, Jul 19, 2012 at 3:34 PM, Raymond Wooninck <tittiatcoke@gmail.com> wrote:
On Thursday, July 19, 2012 14:38:47 todd rme wrote:
On Thu, Jul 19, 2012 at 12:37 PM, Will Stephenson <wstephenson@suse.de> wrote:
On Tuesday 17 Jul 2012 13:49:06 todd rme wrote:
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Done, and you are maintainer.
Great! Thanks!
Please add qualified contributors too.
How do I decide who is qualified?
I am not trying to be sarcastic here, I have done a lot of work making packages, but I have no experience with those sorts of administrative decisions.
-Todd
Hi Todd,
Please validate also the patches that are in KDF if they should be there for KR49 as well. I have tried my best to keep the patches in KUSC as up to date as possible, but didn't track any new patches that were pushed into KDF.
Raymond
Will do. The repo is set up and the packages are imported, but there are certainly some mistakes, missing packages, packages that need newer versions, etc. I've already added two new packages (pairs and svgpart), and changed the names of several packages to match upstream naming changes (likgoogle, libmm-qt, libnm-qt). There are still a few things that I think are likely wrong: 1. svgpart may not be the best name. It is the upstream name but doesn't clearly connect it to KDE 2. Some packages might need version updates compared to what is in KDF. I tried to link to KDF as much as possible, but I already had to update akonadi-runtime, and there may be others I missed 3. Some packages may no longer be needed. I plan to ultimately enable building for openSUSE 11.4 if possible, but only after the official release. Therefore there are some 11.4-only packages that are disabled right now. But besides that there may be some others that are just obsolete (I already removed akonadi-google, and obsoleted in kde4-filesystem). 4. I may have just messed something up, forgot to save the .changes entry, forgot a file, or something. 5. Raymond's before-mentioned patch issue. 6. There is still a wallpapers package in the upstream source repo that I have not had time to deal with. So anyone who is willing to check would be helpful. Publishing is obviously disabled for now. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri 20 Jul 2012 10:53:59 todd rme wrote:
On Thu, Jul 19, 2012 at 3:34 PM, Raymond Wooninck <tittiatcoke@gmail.com> wrote:
On Thursday, July 19, 2012 14:38:47 todd rme wrote:
On Thu, Jul 19, 2012 at 12:37 PM, Will Stephenson <wstephenson@suse.de>
wrote:
On Tuesday 17 Jul 2012 13:49:06 todd rme wrote:
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Done, and you are maintainer.
Great! Thanks!
Please add qualified contributors too.
How do I decide who is qualified?
I am not trying to be sarcastic here, I have done a lot of work making packages, but I have no experience with those sorts of administrative decisions.
-Todd
Hi Todd,
Please validate also the patches that are in KDF if they should be there for KR49 as well. I have tried my best to keep the patches in KUSC as up to date as possible, but didn't track any new patches that were pushed into KDF.
Raymond
Will do. The repo is set up and the packages are imported, but there are certainly some mistakes, missing packages, packages that need newer versions, etc. I've already added two new packages (pairs and svgpart), and changed the names of several packages to match upstream naming changes (likgoogle, libmm-qt, libnm-qt).
There are still a few things that I think are likely wrong:
1. svgpart may not be the best name. It is the upstream name but doesn't clearly connect it to KDE 2. Some packages might need version updates compared to what is in KDF. I tried to link to KDF as much as possible, but I already had to update akonadi-runtime, and there may be others I missed 3. Some packages may no longer be needed. I plan to ultimately enable building for openSUSE 11.4 if possible, but only after the official release. Therefore there are some 11.4-only packages that are disabled right now. But besides that there may be some others that are just obsolete (I already removed akonadi-google, and obsoleted in kde4-filesystem). 4. I may have just messed something up, forgot to save the .changes entry, forgot a file, or something. 5. Raymond's before-mentioned patch issue. 6. There is still a wallpapers package in the upstream source repo that I have not had time to deal with.
So anyone who is willing to check would be helpful. Publishing is obviously disabled for now.
-Todd
some of the changes Raymond already did in his home project. https://build.opensuse.org/project/show?project=home%3Arwooninck%3AUNSTABLE_... https://build.opensuse.org/project/show?project=home%3Arwooninck%3AUNSTABLE_... Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday 20 Jul 2012 10:53:59 todd rme wrote:
On Thu, Jul 19, 2012 at 3:34 PM, Raymond Wooninck <tittiatcoke@gmail.com> wrote:
On Thursday, July 19, 2012 14:38:47 todd rme wrote:
On Thu, Jul 19, 2012 at 12:37 PM, Will Stephenson <wstephenson@suse.de>
wrote:
On Tuesday 17 Jul 2012 13:49:06 todd rme wrote:
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Done, and you are maintainer.
Great! Thanks!
Please add qualified contributors too.
How do I decide who is qualified?
I am not trying to be sarcastic here, I have done a lot of work making packages, but I have no experience with those sorts of administrative decisions.
-Todd
Hi Todd,
Please validate also the patches that are in KDF if they should be there for KR49 as well. I have tried my best to keep the patches in KUSC as up to date as possible, but didn't track any new patches that were pushed into KDF.
Raymond
Will do. The repo is set up and the packages are imported, but there are certainly some mistakes, missing packages, packages that need newer versions, etc. I've already added two new packages (pairs and svgpart), and changed the names of several packages to match upstream naming changes (likgoogle, libmm-qt, libnm-qt).
Great work! Thanks for taking this on and getting yourself started so well Please keep a note of package renames/removes vs KDF so when we move this to KDF and make it links, it goes as smoothly as possible.
There are still a few things that I think are likely wrong:
1. svgpart may not be the best name. It is the upstream name but doesn't clearly connect it to KDE
kde-kpart-svg?
2. Some packages might need version updates compared to what is in KDF. I tried to link to KDF as much as possible, but I already had to update akonadi-runtime, and there may be others I missed
That's ok, just do them as needed.
3. Some packages may no longer be needed. I plan to ultimately enable building for openSUSE 11.4 if possible, but only after the official release. Therefore there are some 11.4-only packages that are disabled right now. But besides that there may be some others that are just obsolete (I already removed akonadi-google, and obsoleted in kde4-filesystem). 4. I may have just messed something up, forgot to save the .changes entry, forgot a file, or something. 5. Raymond's before-mentioned patch issue. 6. There is still a wallpapers package in the upstream source repo that I have not had time to deal with.
These are business-as-usual problems - you'll get through them. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri, Jul 20, 2012 at 1:20 PM, Will Stephenson <wstephenson@suse.de> wrote:
On Friday 20 Jul 2012 10:53:59 todd rme wrote:
Will do. The repo is set up and the packages are imported, but there are certainly some mistakes, missing packages, packages that need newer versions, etc. I've already added two new packages (pairs and svgpart), and changed the names of several packages to match upstream naming changes (likgoogle, libmm-qt, libnm-qt).
Great work! Thanks for taking this on and getting yourself started so well
Thanks
Please keep a note of package renames/removes vs KDF so when we move this to KDF and make it links, it goes as smoothly as possible.
So far there is only one, but I will put them all in kde4-filesystem. Most of the renames are relative to KDE:Unstable:SC, and those packages do not exist anywhere else (except for a few home projects). The actual RPM names are the same, so they can be moved to KDE:Unstable:SC without needing to change any other packages. My plan is to submit all non-KDE-SC libraries to KDF as soon as they build successfully, since they won't disrupt any existing KDE packages.
There are still a few things that I think are likely wrong:
1. svgpart may not be the best name. It is the upstream name but doesn't clearly connect it to KDE
kde-kpart-svg?
That occurred to me, but if that is the case might we want to rename webkitpart also?
2. Some packages might need version updates compared to what is in KDF. I tried to link to KDF as much as possible, but I already had to update akonadi-runtime, and there may be others I missed
That's ok, just do them as needed.
[snip]
These are business-as-usual problems - you'll get through them.
Indeed. This was more in case anyone else was planning to look so they knew where they could focus their attention.
Will -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri, Jul 20, 2012 at 10:53 AM, todd rme <toddrme2178@gmail.com> wrote:
On Thu, Jul 19, 2012 at 3:34 PM, Raymond Wooninck <tittiatcoke@gmail.com> wrote:
On Thursday, July 19, 2012 14:38:47 todd rme wrote:
On Thu, Jul 19, 2012 at 12:37 PM, Will Stephenson <wstephenson@suse.de> wrote:
On Tuesday 17 Jul 2012 13:49:06 todd rme wrote:
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Done, and you are maintainer.
Great! Thanks!
Please add qualified contributors too.
How do I decide who is qualified?
I am not trying to be sarcastic here, I have done a lot of work making packages, but I have no experience with those sorts of administrative decisions.
-Todd
Hi Todd,
Please validate also the patches that are in KDF if they should be there for KR49 as well. I have tried my best to keep the patches in KUSC as up to date as possible, but didn't track any new patches that were pushed into KDF.
Raymond
Will do. The repo is set up and the packages are imported, but there are certainly some mistakes, missing packages, packages that need newer versions, etc. I've already added two new packages (pairs and svgpart), and changed the names of several packages to match upstream naming changes (likgoogle, libmm-qt, libnm-qt).
There are still a few things that I think are likely wrong:
1. svgpart may not be the best name. It is the upstream name but doesn't clearly connect it to KDE 2. Some packages might need version updates compared to what is in KDF. I tried to link to KDF as much as possible, but I already had to update akonadi-runtime, and there may be others I missed 3. Some packages may no longer be needed. I plan to ultimately enable building for openSUSE 11.4 if possible, but only after the official release. Therefore there are some 11.4-only packages that are disabled right now. But besides that there may be some others that are just obsolete (I already removed akonadi-google, and obsoleted in kde4-filesystem). 4. I may have just messed something up, forgot to save the .changes entry, forgot a file, or something. 5. Raymond's before-mentioned patch issue. 6. There is still a wallpapers package in the upstream source repo that I have not had time to deal with.
So anyone who is willing to check would be helpful. Publishing is obviously disabled for now.
-Todd
I noticed that the KDE package sources do not have the full URL to the download. Is there a reason for this or should I add it? Also, can I remove the xz buildrequires now? Neither KDF nor KR49 need it anymore. Someone said not to build against openSUSE 11.4, since it is eol soon. Are we never going to build these packages against openSUSE 11.4, and if so can I remove the build checks for it? -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday, July 20, 2012 20:16:04 todd rme wrote:
I noticed that the KDE package sources do not have the full URL to the download. Is there a reason for this or should I add it?
Also, can I remove the xz buildrequires now? Neither KDF nor KR49 need it anymore.
Someone said not to build against openSUSE 11.4, since it is eol soon. Are we never going to build these packages against openSUSE 11.4, and if so can I remove the build checks for it? Hi Todd,
I wouldn't remove openSUSE 11.4 support right now. People running 11.4, might still want to install KDE 4.9 :-) The builldrequires for xz was required as that the sources in KDF were packaged with xz. This would deliver a smaller tarball. If you create packages with bzip2, then the xz buildrequire is indeed not required. I noticed that you are submitting libraries already to KDF. For libQtModemManager and libQtNetworkManager, please update the tarball to the latest version in git (at least if you are planning to deliver also the latest version of the networkmanagement plasmoid). Thanks for your help. Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
and for targets with networkmanager 0.9.4 you need a plasmoid after 20/07/12, as previous it was some bug that did not allow you to create wireless connections. Alin -- Without Questions there are no Answers! ______________________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin ---- Ardionsamblú Móilíneach Saotharlann Taighde Scoil na Fisice, An Coláiste Ollscoile, Baile Átha Cliath ----------------------------------------------------------------------------------- http://alin.elenaworld.net ______________________________________________________________________ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Jul 22, 2012 at 9:45 AM, Raymond Wooninck <tittiatcoke@gmail.com> wrote:
On Friday, July 20, 2012 20:16:04 todd rme wrote:
I noticed that the KDE package sources do not have the full URL to the download. Is there a reason for this or should I add it?
Also, can I remove the xz buildrequires now? Neither KDF nor KR49 need it anymore.
Someone said not to build against openSUSE 11.4, since it is eol soon. Are we never going to build these packages against openSUSE 11.4, and if so can I remove the build checks for it? Hi Todd,
I wouldn't remove openSUSE 11.4 support right now. People running 11.4, might still want to install KDE 4.9 :-)
Sven Burmeister said not to (due to the impending eol), that is why I am asking.
The builldrequires for xz was required as that the sources in KDF were packaged with xz. This would deliver a smaller tarball. If you create packages with bzip2, then the xz buildrequire is indeed not required.
KDF, KR48, and KR49 all have "Support: xz" in their project config, so if I understand it correctly all packages in those repos will get xz whether it is a buildrequires or not. So having it as a buildrequires is redundant. That is why I am asking if I can remove it.
I noticed that you are submitting libraries already to KDF. For libQtModemManager and libQtNetworkManager, please update the tarball to the latest version in git (at least if you are planning to deliver also the latest version of the networkmanagement plasmoid).
Should I use the git version of networkmanager, or should I just stick to the stable version? Networkmanager releases are not synced to KDE SC releases, so that may be outside the scope of this.
Thanks for your help.
Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 22. Juli 2012, 11:31:28 schrieb todd rme:
I wouldn't remove openSUSE 11.4 support right now. People running 11.4, might still want to install KDE 4.9 :-)
Sven Burmeister said not to (due to the impending eol), that is why I am asking.
Yep. 11.4 will be eol before 4.9 gets its minor updates so what's the point of starting to support something which will be dropped in the middle? Also it puts an extra load on the already overloaded obs, especially since you picked Factory which is usually not part of an KRxy repo, since it is an unstable "release". Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 2012/07/22 16:08 (GMT+0200) Sven Burmeister composed:
todd rme wrote:
I wouldn't remove openSUSE 11.4 support right now. People running 11.4, might still want to install KDE 4.9 :-)
Sven Burmeister said not to (due to the impending eol), that is why I am asking.
Yep. 11.4 will be eol before 4.9 gets its minor updates
Are you sure? 12.2 release is still well over a month away.
so what's the point of starting to support something which will be dropped in the middle?
Evergreen. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 22. Juli 2012, 10:21:51 schrieb Felix Miata:
so what's the point of starting to support something which will be dropped in the middle? Evergreen.
So let the Evergreen guys take care of spamming obs even more. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Jul 22, 2012 at 4:21 PM, Felix Miata <mrmazda@earthlink.net> wrote:
On 2012/07/22 16:08 (GMT+0200) Sven Burmeister composed:
todd rme wrote:
I wouldn't remove openSUSE 11.4 support right now. People running 11.4, might still want to install KDE 4.9 :-)
Sven Burmeister said not to (due to the impending eol), that is why I am asking.
so what's the point of starting to support something which will be dropped in the middle?
Evergreen.
Are we planning on supporting evergreen in the KR repos? I would think that would be a big burden on the project maintainers and on OBS. It isn't just build targets, the entire KR46 repo would need to be kept active. Are people who are sticking with a 3-year old release really going to want a bleeding-edge KDE release? Especially since it will pull in new libraries and updated versions of old libraries, potentially destabilizing the system. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Jul 22, 2012 at 4:08 PM, Sven Burmeister <sven.burmeister@gmx.net> wrote:
Am Sonntag, 22. Juli 2012, 11:31:28 schrieb todd rme:
I wouldn't remove openSUSE 11.4 support right now. People running 11.4, might still want to install KDE 4.9 :-)
Sven Burmeister said not to (due to the impending eol), that is why I am asking.
Yep. 11.4 will be eol before 4.9 gets its minor updates so what's the point of starting to support something which will be dropped in the middle?
Also it puts an extra load on the already overloaded obs, especially since you picked Factory which is usually not part of an KRxy repo, since it is an unstable "release".
Sven
I have no particular side in this. Building for openSUSE 11.4 is not just a matter of enabling repos, however, since it also requires a number of additional packages that are available by default in openSUSE 12.1 and later. There is nothing to prevent this, in fact the packages in question are already in the KR49 repo, just disabled. I will let people more knowledgeable and more experienced than me make that call. However, I plan to clean up the spec files prior to merging everything back to KDF, so the sooner I know whether I should remove openSUSE 11.4 references the better. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag 22 Juli 2012, 11:31:28 schrieb todd rme:
Should I use the git version of networkmanager, or should I just stick to the stable version? Networkmanager releases are not synced to KDE SC releases, so that may be outside the scope of this.
Use release versions but put new versions in KR49 once they are released. Git snapshots should be put in Playground IMHO. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Freitag 20 Juli 2012, 10:53:59 schrieb todd rme:
2. Some packages might need version updates compared to what is in KDF. I tried to link to KDF as much as possible, but I already had to update akonadi-runtime, and there may be others I missed
If by doing so Calligra 2.5 will eventually end up there automatically, OK. If not, Calligra 2.5 may be an option to update (it's currently RC just like SC 4.9).
3. Some packages may no longer be needed. For the sake of OBS load, maybe a few packages, that are officially part of SC 4.x but actually no longer maintained, could be dropped. Kscd and KFloppy come to mind. Amarok respectively YaST have their functionality anyway. kupdateapplet has been replaced by Apper, IIRC.
OTOH LightDM-KDE may be a worthwhile addition: http://www.sharpley.org.uk/blog/lightdm-0_2 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Jul 22, 2012 at 7:10 PM, Markus <kamikazow@gmx.de> wrote:
Am Freitag 20 Juli 2012, 10:53:59 schrieb todd rme:
2. Some packages might need version updates compared to what is in KDF. I tried to link to KDF as much as possible, but I already had to update akonadi-runtime, and there may be others I missed
If by doing so Calligra 2.5 will eventually end up there automatically, OK. If not, Calligra 2.5 may be an option to update (it's currently RC just like SC 4.9).
Besides KDE SC and any dependencies, I think the proper place for unstable packages is KDE:Unstable:Playground.
3. Some packages may no longer be needed. For the sake of OBS load, maybe a few packages, that are officially part of SC 4.x but actually no longer maintained, could be dropped. Kscd and KFloppy come to mind. Amarok respectively YaST have their functionality anyway. kupdateapplet has been replaced by Apper, IIRC.
I am building the packages that are built in KDF. If we want to remove packages from KDF, that should probably be discussed in another thread. Looking at the git log, however, kscd is being maintained. It isn't getting heavy development, but it is getting some fixes here and there. Even kfloppy is getting occasional commits. Whether they are useful is another question. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Mittwoch 25 Juli 2012, 09:56:39 schrieb todd rme:
If by doing so Calligra 2.5 will eventually end up there automatically, OK. If not, Calligra 2.5 may be an option to update (it's currently RC just like SC 4.9).
Besides KDE SC and any dependencies, I think the proper place for unstable packages is KDE:Unstable:Playground.
You were usually right but Calligra 2.5 should be released around the same time as the final SC 4.9, so it might make sense to prepare for that release as well. But as I said: If updating Calligra in Factory means that KR49 will also be updated, my comment is invalid. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Wednesday 25 Jul 2012 13:02:27 Markus wrote:
Am Mittwoch 25 Juli 2012, 09:56:39 schrieb todd rme:
If by doing so Calligra 2.5 will eventually end up there automatically, OK. If not, Calligra 2.5 may be an option to update (it's currently RC just like SC 4.9).
Besides KDE SC and any dependencies, I think the proper place for unstable packages is KDE:Unstable:Playground.
You were usually right but Calligra 2.5 should be released around the same time as the final SC 4.9, so it might make sense to prepare for that release as well. But as I said: If updating Calligra in Factory means that KR49 will also be updated, my comment is invalid.
It seems that Calligra 2.4.3 doesn't build with KDE 4.9 anyway, see: https://build.opensuse.org/package/live_build_log?arch=i586&package=calligra&project=KDE%3ARelease%3A49&repository=openSUSE_12.1 So using 2.5 RC ist probably the best way to go ... I'd rather prepare the new Calligra now in KR49 (as is done with KDE 4.9), then push it to KDF once openSUSE 12.2 is out and KDF available for additions again. Afterwards it is as you said - KR49 will link to KDF as long as KDE 4.9 is in there and thus gets all the updates as well. Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri, Jul 27, 2012 at 9:27 AM, Nico Kruber <nico.kruber@gmail.com> wrote:
On Wednesday 25 Jul 2012 13:02:27 Markus wrote:
Am Mittwoch 25 Juli 2012, 09:56:39 schrieb todd rme:
If by doing so Calligra 2.5 will eventually end up there automatically, OK. If not, Calligra 2.5 may be an option to update (it's currently RC just like SC 4.9).
Besides KDE SC and any dependencies, I think the proper place for unstable packages is KDE:Unstable:Playground.
You were usually right but Calligra 2.5 should be released around the same time as the final SC 4.9, so it might make sense to prepare for that release as well. But as I said: If updating Calligra in Factory means that KR49 will also be updated, my comment is invalid.
It seems that Calligra 2.4.3 doesn't build with KDE 4.9 anyway, see:
So using 2.5 RC ist probably the best way to go ... I'd rather prepare the new Calligra now in KR49 (as is done with KDE 4.9), then push it to KDF once openSUSE 12.2 is out and KDF available for additions again. Afterwards it is as you said - KR49 will link to KDF as long as KDE 4.9 is in there and thus gets all the updates as well.
Yeah, I saw that too. I am building the RC now. I will push it soon if it builds. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 17 July 2012 13:49:06 todd rme wrote:
On Tue, Jul 17, 2012 at 1:46 PM, Sven Burmeister
<sven.burmeister@gmx.net> wrote:
Am Dienstag, 17. Juli 2012, 21:02:34 schrieb doiggl@velocitynet.com.au:
Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97, source packages listed at [2] Relese notice at [3].
The maintainer (not paid by openSUSE) is on holiday and nobody else seems to bother updating the repo. So unless you feel like updating the repo with the new sources etc. you will have to wait until somebody else does so.
Sven
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Did you give up? Every package is listed as disabled in the repo. What's going on? Anders -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Wednesday 25 Jul 2012 19:54:25 Anders Johansson wrote:
On Tuesday 17 July 2012 13:49:06 todd rme wrote:
On Tue, Jul 17, 2012 at 1:46 PM, Sven Burmeister
<sven.burmeister@gmx.net> wrote:
Am Dienstag, 17. Juli 2012, 21:02:34 schrieb doiggl@velocitynet.com.au:
Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97, source packages listed at [2] Relese notice at [3].
The maintainer (not paid by openSUSE) is on holiday and nobody else seems to bother updating the repo. So unless you feel like updating the repo with the new sources etc. you will have to wait until somebody else does so.
Sven
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Did you give up? Every package is listed as disabled in the repo. What's going on?
packages are building just fine now build was previously only enabled for a few repos to save build power on OBS while the packaging scripts were being updated Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thu, Jul 26, 2012 at 10:12 AM, Nico Kruber <nico.kruber@gmail.com> wrote:
On Wednesday 25 Jul 2012 19:54:25 Anders Johansson wrote:
On Tuesday 17 July 2012 13:49:06 todd rme wrote:
On Tue, Jul 17, 2012 at 1:46 PM, Sven Burmeister
<sven.burmeister@gmx.net> wrote:
Am Dienstag, 17. Juli 2012, 21:02:34 schrieb doiggl@velocitynet.com.au:
Can the KDE:Unstable:SC packages[1] be updated to version 4.8.97, source packages listed at [2] Relese notice at [3].
The maintainer (not paid by openSUSE) is on holiday and nobody else seems to bother updating the repo. So unless you feel like updating the repo with the new sources etc. you will have to wait until somebody else does so.
Sven
Might it be time now to setup a KDE:Release:49 repo? I would be willing to help.
Did you give up? Every package is listed as disabled in the repo. What's going on?
packages are building just fine now
build was previously only enabled for a few repos to save build power on OBS while the packaging scripts were being updated
Nico
Exactly. When core packages (kdelibs4, kdebase4-workspace) are changed, large numbers of other packages rebuild. So I had most of the repos disabled until those were working. Now building is enabled. Once I confirm it is building at least on 12.1 and Factory I will enable publishing. Once everything is published once I will start working on making improvements and other minor fixes to the packages. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag 26 Juli 2012, 12:27:41 schrieb todd rme:
Exactly. When core packages (kdelibs4, kdebase4-workspace) are changed, large numbers of other packages rebuild. So I had most of the repos disabled until those were working. Now building is enabled. Once I confirm it is building at least on 12.1 and Factory I will enable publishing. Once everything is published once I will start working on making improvements and other minor fixes to the packages.
You rock! Thank you a lot. Do the packages build with libHUpnp1 support? I'm asking because currently everything crashed when I'm connected to my university's WiFi: https://bugzilla.novell.com/show_bug.cgi?id=768368 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Donnerstag, 26. Juli 2012, 12:27:41 schrieb todd rme:
Exactly. When core packages (kdelibs4, kdebase4-workspace) are changed, large numbers of other packages rebuild. So I had most of the repos disabled until those were working.
Given how people waste obs' resources, kudos for that workflow!
Now building is enabled. Once I confirm it is building at least on 12.1 and Factory I will enable publishing.
Could you please enable publishuing for 12.1 i586 already since it is almost finished and the other archs will take at least a day or two to finish building. Thanks! Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thu, Jul 26, 2012 at 10:21 PM, Sven Burmeister <sven.burmeister@gmx.net> wrote:
Am Donnerstag, 26. Juli 2012, 12:27:41 schrieb todd rme:
Exactly. When core packages (kdelibs4, kdebase4-workspace) are changed, large numbers of other packages rebuild. So I had most of the repos disabled until those were working.
Given how people waste obs' resources, kudos for that workflow!
Thanks
Now building is enabled. Once I confirm it is building at least on 12.1 and Factory I will enable publishing.
Could you please enable publishuing for 12.1 i586 already since it is almost finished and the other archs will take at least a day or two to finish building.
Thanks!
Sven
x86_64 is nearly done as well, so I just enabled publishing for 12.1 in general. Factory/12.2 has a problem with one package that 12.1 doesn't have, anyway. In other news, there seems to be a problem with nepomuk-virtuoso-convertor. How many years has it been since the switch? Do we really need that anymore? I am really not sure it is worth the time fixing it at this point. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
I saw that, too, but then I checked KDF and the package is disabled there as well, so I guess, we could disable it for KR49, too. Nico On Friday 27 Jul 2012 09:45:16 todd rme wrote:
In other news, there seems to be a problem with nepomuk-virtuoso-convertor. How many years has it been since the switch? Do we really need that anymore? I am really not sure it is worth the time fixing it at this point.
-Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri, Jul 27, 2012 at 10:36 AM, Nico Kruber <nico.kruber@gmail.com> wrote:
In other news, there seems to be a problem with nepomuk-virtuoso-convertor. How many years has it been since the switch? Do we really need that anymore? I am really not sure it is worth the time fixing it at this point.
-Todd I saw that, too, but then I checked KDF and the package is disabled there as well, so I guess, we could disable it for KR49, too.
Nico
Done -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Friday, July 27, 2012 11:14:34 todd rme wrote:
On Fri, Jul 27, 2012 at 10:36 AM, Nico Kruber <nico.kruber@gmail.com> wrote:
In other news, there seems to be a problem with nepomuk-virtuoso-convertor. How many years has it been since the switch? Do we really need that anymore? I am really not sure it is worth the time fixing it at this point.
Hi Todd, You can easily remove that package from the repository. It is no longer needed and I guess we were all too lazy (or to busy with other things) to remove it :-) Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 07/27/2012 11:45 AM, Raymond Wooninck wrote:
On Friday, July 27, 2012 11:14:34 todd rme wrote:
On Fri, Jul 27, 2012 at 10:36 AM, Nico Kruber <nico.kruber@gmail.com> wrote:
In other news, there seems to be a problem with nepomuk-virtuoso-convertor. How many years has it been since the switch? Do we really need that anymore? I am really not sure it is worth the time fixing it at this point.
Hi Todd,
You can easily remove that package from the repository. It is no longer needed and I guess we were all too lazy (or to busy with other things) to remove it :-)
Int that case: please add provides/obsoletes somewhere, so that it gets removed from installations as well, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter/Identica: jaegerandi SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn,Jennifer Guild,Felix Imendörffer,HRB16746 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Fri, Jul 27, 2012 at 12:04 PM, Andreas Jaeger <aj@suse.com> wrote:
On 07/27/2012 11:45 AM, Raymond Wooninck wrote:
On Friday, July 27, 2012 11:14:34 todd rme wrote:
On Fri, Jul 27, 2012 at 10:36 AM, Nico Kruber <nico.kruber@gmail.com> wrote:
In other news, there seems to be a problem with nepomuk-virtuoso-convertor. How many years has it been since the switch? Do we really need that anymore? I am really not sure it is worth the time fixing it at this point.
Hi Todd,
You can easily remove that package from the repository. It is no longer needed and I guess we were all too lazy (or to busy with other things) to remove it :-)
Int that case: please add provides/obsoletes somewhere, so that it gets removed from installations as well,
Andreas
I'll do so, but I have to wait until everything is published. I don't want to restart the entire build when several targets are just a few packages away from being done. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Freitag, 27. Juli 2012, 09:45:16 schrieb todd rme:
x86_64 is nearly done as well, so I just enabled publishing for 12.1 in general. Factory/12.2 has a problem with one package that 12.1 doesn't have, anyway.
I updated and found three small issues: 1. AFAIK KDE 4.9 must not be used with virtuoso 6.1.5 but only .4 or .6 (to be released soon [since a week or more]) 2. debuginfo packages are not enabled 3. kdebase4-workspace-branding-openSUSE seems to be missing and is not obsoleted, at least for 12.1 x64. Everything else seems to be on spot. Well done! Sven PS: Let's hope obs allows to build 4.9 final in less than a week. :| -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 28/07/12 08:18, Sven Burmeister wrote:
Am Freitag, 27. Juli 2012, 09:45:16 schrieb todd rme:
x86_64 is nearly done as well, so I just enabled publishing for 12.1 in general. Factory/12.2 has a problem with one package that 12.1 doesn't have, anyway. I updated and found three small issues:
1. AFAIK KDE 4.9 must not be used with virtuoso 6.1.5 but only .4 or .6 (to be released soon [since a week or more]) 2. debuginfo packages are not enabled 3. kdebase4-workspace-branding-openSUSE seems to be missing and is not obsoleted, at least for 12.1 x64.
Everything else seems to be on spot.
Well done!
Sven
PS: Let's hope obs allows to build 4.9 final in less than a week. :|
Working well here in 12.1 Thanks -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Saturday 28 Jul 2012 09:18:21 Sven Burmeister wrote:
Am Freitag, 27. Juli 2012, 09:45:16 schrieb todd rme:
x86_64 is nearly done as well, so I just enabled publishing for 12.1 in general. Factory/12.2 has a problem with one package that 12.1 doesn't have, anyway.
I updated and found three small issues:
1. AFAIK KDE 4.9 must not be used with virtuoso 6.1.5 but only .4 or .6 (to be released soon [since a week or more])
I guess, we have to wait for 6.1.6 then or is there a 6.1.5 package with the according patches somewhere in OBS yet? last mail from Will about this suggested that the openSUSE patches for this are not fully correct yet
2. debuginfo packages are not enabled
enabled now
3. kdebase4-workspace-branding-openSUSE seems to be missing and is not obsoleted, at least for 12.1 x64.
I added this package again Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Samstag, 28. Juli 2012, 12:11:45 schrieb Nico Kruber:
3. kdebase4-workspace-branding-openSUSE seems to be missing and is not obsoleted, at least for 12.1 x64.
There are a few more missing compared to KR48 and KDF. Probably on purpose. kdevelop, yakuake, konversation, kaffeine, skanlite, ktorrent etc. I think those are part of oss and hence not KDE:Extra. Also libkdcraw20, libmarbelwidget13, libkipi8 and libkexiv2-10 are not obsoleted or lacking from the KR49 repo. Thanks! Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Saturday, July 28, 2012 12:55:51 Sven Burmeister wrote:
Also libkdcraw20, libmarbelwidget13, libkipi8 and libkexiv2-10 are not obsoleted or lacking from the KR49 repo.
These shared libraries will never be obsoleted. This is due to the policy around packages with libraries. For KR49 you should have libmarblewidget14, libkipi9, libkexiv2-11 and libkdcraw21. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Samstag, 28. Juli 2012, 12:59:19 schrieb Raymond Wooninck:
These shared libraries will never be obsoleted. This is due to the policy around packages with libraries. For KR49 you should have libmarblewidget14, libkipi9, libkexiv2-11 and libkdcraw21.
Ok. Isn't there anything one can do not to get more and more of these obsolete packages? Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Saturday, July 28, 2012 14:22:41 Sven Burmeister wrote:
Ok. Isn't there anything one can do not to get more and more of these obsolete packages?
Manual clean-up of those libraries :-) This has been raised a couple of times (we have more of these libraries outside of KDE, e.g. libx264) and the answer was always that they can not be made obsolete as that you never know if an older program installed doesn't need them anymore.. Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On 28/07/12 20:31, Raymond Wooninck wrote:
Ok. Isn't there anything one can do not to get more and more of these obsolete packages? Manual clean-up of those libraries :-) This has been raised a couple of times (we have more of these libraries outside of KDE, e.g. libx264) and the answer was always that they can not be made obsolete as that you never know if an
On Saturday, July 28, 2012 14:22:41 Sven Burmeister wrote: older program installed doesn't need them anymore..
Raymond FYI the konsole is defaulting to ~/Documents> -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Jul 29, 2012 at 9:14 AM, Carl Fletcher <kernelcruncher@gmail.com> wrote:
On 28/07/12 20:31, Raymond Wooninck wrote:
On Saturday, July 28, 2012 14:22:41 Sven Burmeister wrote:
Ok. Isn't there anything one can do not to get more and more of these obsolete packages?
Manual clean-up of those libraries :-) This has been raised a couple of times (we have more of these libraries outside of KDE, e.g. libx264) and the answer was always that they can not be made obsolete as that you never know if an older program installed doesn't need them anymore..
Raymond
FYI the konsole is defaulting to ~/Documents>
I know there are some fixed that need to be done, but let's hold off on any changes until the KR49 openSUSE 12.1 packages for KDE:Extra are published for openSUSE 12.1. I will submit a fixed calligra soon, but for everything else I would prefer to have a complete set of packages in the repos before we start things rebuilding again, otherwise it will never get published. At the present rate, by the time another complete rebuild is done, KDE SC 49 final will be out. That will require at least another complete rebuild. So if we don't get everything published now, it will likely be at least another week before it can be published. Once the repos that build off KR49 are published people will be able to start using it fully. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sunday 29 Jul 2012 12:11:02 todd rme wrote:
At the present rate, by the time another complete rebuild is done, KDE SC 49 final will be out. That will require at least another complete rebuild. So if we don't get everything published now, it will likely be at least another week before it can be published. Once the repos that build off KR49 are published people will be able to start using it fully.
Speaking of 4.9.0 final, the final tarballs have been available privately to kde-packagers since Thursday but we still have 4.8.97 in KR49. Does Todd or anyone else maintaining KR49 have access to the kde-packagers mailing list and download location? If not, send me your public ssh keys and I will arrange that. Do you want me to use my access to update to those final tarballs so that we have a shot of a complete build by release day? Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sun, Jul 29, 2012 at 11:02 PM, Will Stephenson <wstephenson@suse.de> wrote:
On Sunday 29 Jul 2012 12:11:02 todd rme wrote:
At the present rate, by the time another complete rebuild is done, KDE SC 49 final will be out. That will require at least another complete rebuild. So if we don't get everything published now, it will likely be at least another week before it can be published. Once the repos that build off KR49 are published people will be able to start using it fully.
Speaking of 4.9.0 final, the final tarballs have been available privately to kde-packagers since Thursday but we still have 4.8.97 in KR49. Does Todd or anyone else maintaining KR49 have access to the kde-packagers mailing list and download location? If not, send me your public ssh keys and I will arrange that.
Do you want me to use my access to update to those final tarballs so that we have a shot of a complete build by release day?
Will
I don't have access, unfortunately. It would be great to get the tarballs in before the official release, but as I said, please at least wait until KDE:Extra is published for KR49 openSUSE 12.1. Otherwise there is no chance of us having a full set of packages until long after the release. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Sonntag, 29. Juli 2012, 23:30:04 schrieb todd rme:
I don't have access, unfortunately. It would be great to get the tarballs in before the official release, but as I said, please at least wait until KDE:Extra is published for KR49 openSUSE 12.1. Otherwise there is no chance of us having a full set of packages until long after the release.
The problem with obs is that if you do not change a package it takes forever to start building, i.e. if it is only rebuilt because deps changed or if it is a link. There might be some other effects, yet if you branch a package building starts instantly. So something is dragging the build prio for KDE repos down. Whatever logic lies behind this, it results in the KDE-repo taking a week to build which IMHO is de-motivating for anyone spending his free time on maintaining it. I might be wrong with that but at least I would be pretty annoyed having to check every few hours just to find that lots of packages are still in "scheduled" mode (for days), or even better "finished" for an hour but not moving forward. Anyhow, the same holds true for Extra. So if you want to get work done, the only chance you have is to ask adrianS on IRC to get a higher build priority temporarily. This was done in the past already and all you need to do is ask. That way you would get Extra finished within half an hour and could start to work on KR49. With build priority, KRxy only takes 2-3 hours max, i.e. you can actually work with it, just in case times runs out before the release date. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Sunday 29 July 2012 23:43:12 Sven Burmeister wrote:
The problem with obs is that if you do not change a package it takes forever to start building, i.e. if it is only rebuilt because deps changed or if it is a link. There might be some other effects, yet if you branch a package building starts instantly. So something is dragging the build prio for KDE repos down.
actually, I think, it is the other way around... iirc, repos with lots of packages and changes get lower build priority. This is why a branched package gets build almost immediately - you normally don't have a full copy of the repo you are branching from asking for (temporarily) higher build priority is probably the best we can do, and a higher priority makes especially sense for preparing a new release of a big software release like KDE to get the packages in shape in time Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Saturday 28 July 2012 12:55:51 Sven Burmeister wrote:
There are a few more missing compared to KR48 and KDF. Probably on purpose. kdevelop, yakuake, konversation, kaffeine, skanlite, ktorrent etc. I think those are part of oss and hence not KDE:Extra.
I added links to the packages from KDF for all these apps - if there are more, please tell me/us Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Saturday 28 Jul 2012 12:11:45 Nico Kruber wrote:
On Saturday 28 Jul 2012 09:18:21 Sven Burmeister wrote:
1. AFAIK KDE 4.9 must not be used with virtuoso 6.1.5 but only .4 or .6 (to be released soon [since a week or more])
I guess, we have to wait for 6.1.6 then or is there a 6.1.5 package with the according patches somewhere in OBS yet? last mail from Will about this suggested that the openSUSE patches for this are not fully correct yet
Since 6.1.6 has not been released yet and I don't know, which patch fixes this issue, I created a branch with the current development snapshot of virtuoso-6 which happens to be RC3 of 6.1.6 - see https://build.opensuse.org/package/show?package=virtuoso&project=home%3ANicoK%3Abranches%3AKDE%3ARelease%3A49 I don't know, whether we should push it to KR49 - I'm waiting for comments on this one here Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 30 Jul 2012 11:10:04 you wrote:
On Saturday 28 Jul 2012 12:11:45 Nico Kruber wrote:
On Saturday 28 Jul 2012 09:18:21 Sven Burmeister wrote:
1. AFAIK KDE 4.9 must not be used with virtuoso 6.1.5 but only .4 or .6 (to be released soon [since a week or more])
I guess, we have to wait for 6.1.6 then or is there a 6.1.5 package with the according patches somewhere in OBS yet? last mail from Will about this suggested that the openSUSE patches for this are not fully correct yet
Since 6.1.6 has not been released yet and I don't know, which patch fixes this issue, I created a branch with the current development snapshot of virtuoso-6 which happens to be RC3 of 6.1.6 - see https://build.opensuse.org/package/show?package=virtuoso&project=home%3ANico K%3Abranches%3AKDE%3ARelease%3A49
I don't know, whether we should push it to KR49 - I'm waiting for comments on this one here
btw: the new virtuoso-6.1.6-rc3 _does_ require a re-build of soprano-backend- virtuoso which I now also linked into that project Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 30 of July 2012 12:48:45 Nico Kruber wrote:
On Monday 30 Jul 2012 11:10:04 you wrote:
On Saturday 28 Jul 2012 12:11:45 Nico Kruber wrote:
On Saturday 28 Jul 2012 09:18:21 Sven Burmeister wrote:
1. AFAIK KDE 4.9 must not be used with virtuoso 6.1.5 but only .4 or .6 (to be released soon [since a week or more])
I guess, we have to wait for 6.1.6 then or is there a 6.1.5 package with the according patches somewhere in OBS yet? last mail from Will about this suggested that the openSUSE patches for this are not fully correct yet
Since 6.1.6 has not been released yet and I don't know, which patch fixes this issue, I created a branch with the current development snapshot of virtuoso-6 which happens to be RC3 of 6.1.6 - see https://build.opensuse.org/package/show?package=virtuoso&project=home%3ANi co K%3Abranches%3AKDE%3ARelease%3A49
I don't know, whether we should push it to KR49 - I'm waiting for comments on this one here
btw: the new virtuoso-6.1.6-rc3 _does_ require a re-build of soprano-backend- virtuoso which I now also linked into that project
Nico Why? Virtuoso isn't even installed when building soprano. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday, July 30, 2012 15:58:40 hrvojes wrote:
btw: the new virtuoso-6.1.6-rc3 _does_ require a re-build of soprano-backend- virtuoso which I now also linked into that project
Why? Virtuoso isn't even installed when building soprano.
I have to agree here ? Only libiodbc is a build require for soprano and it's backends. Also the virtuoso-server package does not provide any development files. What I can imagine is that we have to make that soprano is on the required version in order to support the 6.1.6 version. In my own kde4 repo, I am building soprano against Factory (with the 6.1.5 version), but actually I am running a 6.1.6 git version from a different repo. And this works fine without any additional rebuild. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 30 Jul 2012 16:09:46 Raymond Wooninck wrote:
What I can imagine is that we have to make that soprano is on the required version in order to support the 6.1.6 version.
what version would that be? -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
If there are no objections I am going to shut down publishing of KR49 to begin uploading the final tarballs once the last couple packages there are done building. Once publishing is disabled, please do NOT enable it again until the official release announcement is made. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Montag, 30. Juli 2012, 18:24:41 schrieb todd rme:
If there are no objections I am going to shut down publishing of KR49 to begin uploading the final tarballs once the last couple packages there are done building. Once publishing is disabled, please do NOT enable it again until the official release announcement is made.
If updating virtuoso only rebuilds virtuoso it might make sense to get that into the repos before shutting it down until the day of the final release. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 30 Jul 2012 18:55:31 Sven Burmeister wrote:
Am Montag, 30. Juli 2012, 18:24:41 schrieb todd rme:
If there are no objections I am going to shut down publishing of KR49 to begin uploading the final tarballs once the last couple packages there are done building. Once publishing is disabled, please do NOT enable it again until the official release announcement is made.
If updating virtuoso only rebuilds virtuoso it might make sense to get that into the repos before shutting it down until the day of the final release.
I created a submitrequest, todd, if you also feel it makes sense, just accept it. I left it in my branch though (even after being accepted) so that we can use it from there is necessary (after publishing disabled) Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Mon, Jul 30, 2012 at 6:58 PM, Nico Kruber <nico.kruber@gmail.com> wrote:
On Monday 30 Jul 2012 18:55:31 Sven Burmeister wrote:
Am Montag, 30. Juli 2012, 18:24:41 schrieb todd rme:
If there are no objections I am going to shut down publishing of KR49 to begin uploading the final tarballs once the last couple packages there are done building. Once publishing is disabled, please do NOT enable it again until the official release announcement is made.
If updating virtuoso only rebuilds virtuoso it might make sense to get that into the repos before shutting it down until the day of the final release.
I created a submitrequest, todd, if you also feel it makes sense, just accept it.
I left it in my branch though (even after being accepted) so that we can use it from there is necessary (after publishing disabled)
Nico
I accepted the request. I will not be able to begin updating until tomorrow anyway. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 30 Jul 2012 19:01:59 todd rme wrote:
On Mon, Jul 30, 2012 at 6:58 PM, Nico Kruber <nico.kruber@gmail.com> wrote:
On Monday 30 Jul 2012 18:55:31 Sven Burmeister wrote:
Am Montag, 30. Juli 2012, 18:24:41 schrieb todd rme:
If there are no objections I am going to shut down publishing of KR49 to begin uploading the final tarballs once the last couple packages there are done building. Once publishing is disabled, please do NOT enable it again until the official release announcement is made.
If updating virtuoso only rebuilds virtuoso it might make sense to get that into the repos before shutting it down until the day of the final release.
I created a submitrequest, todd, if you also feel it makes sense, just accept it.
I left it in my branch though (even after being accepted) so that we can use it from there is necessary (after publishing disabled)
I accepted the request. I will not be able to begin updating until tomorrow anyway.
unfortunately now everything is rebuilding because KDF is getting 4.8.5 and our packages are links to those :( Since it is rebuilding anyway, I'd say, don't wait for that to finish and update afterwards but instead just keep going - if it is doing a complete build it might as well be 4.9 final :) Nico PS: I had to restore a patch for kdelibs4 that apparently got fixed in 4.8.5 but is still in 4.8.97 - please check whether this is still valid in 4.9.0 (solid_udisks_upower_fix_properties.diff) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tue, Jul 31, 2012 at 9:36 AM, Nico Kruber <nico.kruber@gmail.com> wrote:
On Monday 30 Jul 2012 19:01:59 todd rme wrote:
On Mon, Jul 30, 2012 at 6:58 PM, Nico Kruber <nico.kruber@gmail.com> wrote:
On Monday 30 Jul 2012 18:55:31 Sven Burmeister wrote:
Am Montag, 30. Juli 2012, 18:24:41 schrieb todd rme:
If there are no objections I am going to shut down publishing of KR49 to begin uploading the final tarballs once the last couple packages there are done building. Once publishing is disabled, please do NOT enable it again until the official release announcement is made.
If updating virtuoso only rebuilds virtuoso it might make sense to get that into the repos before shutting it down until the day of the final release.
I created a submitrequest, todd, if you also feel it makes sense, just accept it.
I left it in my branch though (even after being accepted) so that we can use it from there is necessary (after publishing disabled)
I accepted the request. I will not be able to begin updating until tomorrow anyway.
unfortunately now everything is rebuilding because KDF is getting 4.8.5 and our packages are links to those :( Since it is rebuilding anyway, I'd say, don't wait for that to finish and update afterwards but instead just keep going - if it is doing a complete build it might as well be 4.9 final :)
I noticed. I already disabled publishing. I will begin pushing updates shortly. Right now I am making sure the non-KDE SC packages are synced between KDF and KR49.
PS: I had to restore a patch for kdelibs4 that apparently got fixed in 4.8.5 but is still in 4.8.97 - please check whether this is still valid in 4.9.0 (solid_udisks_upower_fix_properties.diff)
It is fixed in 4.9, I removed it from my local copy yesterday. I will be pushing the kdelibs4 update first. -Todd -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 31 of July 2012 10:10:41 todd rme wrote:
On Tue, Jul 31, 2012 at 9:36 AM, Nico Kruber <nico.kruber@gmail.com> wrote:
On Monday 30 Jul 2012 19:01:59 todd rme wrote:
On Mon, Jul 30, 2012 at 6:58 PM, Nico Kruber <nico.kruber@gmail.com> wrote:
On Monday 30 Jul 2012 18:55:31 Sven Burmeister wrote:
Am Montag, 30. Juli 2012, 18:24:41 schrieb todd rme:
If there are no objections I am going to shut down publishing of KR49 to begin uploading the final tarballs once the last couple packages there are done building. Once publishing is disabled, please do NOT enable it again until the official release announcement is made.
If updating virtuoso only rebuilds virtuoso it might make sense to get that into the repos before shutting it down until the day of the final release.
I created a submitrequest, todd, if you also feel it makes sense, just accept it.
I left it in my branch though (even after being accepted) so that we can use it from there is necessary (after publishing disabled)
I accepted the request. I will not be able to begin updating until tomorrow anyway.
unfortunately now everything is rebuilding because KDF is getting 4.8.5 and our packages are links to those :( Since it is rebuilding anyway, I'd say, don't wait for that to finish and update afterwards but instead just keep going - if it is doing a complete build it might as well be 4.9 final :)
I noticed. I already disabled publishing. I will begin pushing updates shortly. Right now I am making sure the non-KDE SC packages are synced between KDF and KR49.
PS: I had to restore a patch for kdelibs4 that apparently got fixed in 4.8.5 but is still in 4.8.97 - please check whether this is still valid in 4.9.0 (solid_udisks_upower_fix_properties.diff)
It is fixed in 4.9, I removed it from my local copy yesterday. I will be pushing the kdelibs4 update first.
-Todd Please include fix for opening indexed mails in kmail: https://git.reviewboard.kde.org/r/105738/ It says submitted, but it's not (see the comments) I've tested it, and it works fine :-) -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 31 Jul 2012 09:36:49 Nico Kruber wrote:
On Monday 30 Jul 2012 19:01:59 todd rme wrote:
On Mon, Jul 30, 2012 at 6:58 PM, Nico Kruber <nico.kruber@gmail.com> wrote:
On Monday 30 Jul 2012 18:55:31 Sven Burmeister wrote:
Am Montag, 30. Juli 2012, 18:24:41 schrieb todd rme:
If there are no objections I am going to shut down publishing of KR49 to begin uploading the final tarballs once the last couple packages there are done building. Once publishing is disabled, please do NOT enable it again until the official release announcement is made.
If updating virtuoso only rebuilds virtuoso it might make sense to get that into the repos before shutting it down until the day of the final release.
I created a submitrequest, todd, if you also feel it makes sense, just accept it.
I left it in my branch though (even after being accepted) so that we can use it from there is necessary (after publishing disabled)
I accepted the request. I will not be able to begin updating until tomorrow anyway.
unfortunately now everything is rebuilding because KDF is getting 4.8.5 and our packages are links to those :(
Use osc triggerreason to discover which packages in KDF cause the rebuild, then use osc setlinkrev -r revision-wanted (or without -r for the latest one) on those packages so they don't trigger further rebuilds. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 30 Jul 2012 15:58:40 hrvojes wrote:
On Monday 30 of July 2012 12:48:45 Nico Kruber wrote:
On Monday 30 Jul 2012 11:10:04 you wrote:
On Saturday 28 Jul 2012 12:11:45 Nico Kruber wrote:
On Saturday 28 Jul 2012 09:18:21 Sven Burmeister wrote:
1. AFAIK KDE 4.9 must not be used with virtuoso 6.1.5 but only .4 or .6 (to be released soon [since a week or more])
I guess, we have to wait for 6.1.6 then or is there a 6.1.5 package with the according patches somewhere in OBS yet? last mail from Will about this suggested that the openSUSE patches for this are not fully correct yet
Since 6.1.6 has not been released yet and I don't know, which patch fixes this issue, I created a branch with the current development snapshot of virtuoso-6 which happens to be RC3 of 6.1.6 - see https://build.opensuse.org/package/show?package=virtuoso&project=home%3A Ni co K%3Abranches%3AKDE%3ARelease%3A49
I don't know, whether we should push it to KR49 - I'm waiting for comments on this one here
btw: the new virtuoso-6.1.6-rc3 _does_ require a re-build of soprano-backend- virtuoso which I now also linked into that project
Nico
Why? Virtuoso isn't even installed when building soprano.
I'm talking about soprano-backend- virtuoso, not soprano Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 30 of July 2012 16:12:31 Nico Kruber wrote:
On Monday 30 Jul 2012 15:58:40 hrvojes wrote:
On Monday 30 of July 2012 12:48:45 Nico Kruber wrote:
On Monday 30 Jul 2012 11:10:04 you wrote:
On Saturday 28 Jul 2012 12:11:45 Nico Kruber wrote:
On Saturday 28 Jul 2012 09:18:21 Sven Burmeister wrote:
1. AFAIK KDE 4.9 must not be used with virtuoso 6.1.5 but only .4 or .6 (to be released soon [since a week or more])
I guess, we have to wait for 6.1.6 then or is there a 6.1.5 package with the according patches somewhere in OBS yet? last mail from Will about this suggested that the openSUSE patches for this are not fully correct yet
Since 6.1.6 has not been released yet and I don't know, which patch fixes this issue, I created a branch with the current development snapshot of virtuoso-6 which happens to be RC3 of 6.1.6 - see https://build.opensuse.org/package/show?package=virtuoso&project=home% 3A Ni co K%3Abranches%3AKDE%3ARelease%3A49
I don't know, whether we should push it to KR49 - I'm waiting for comments on this one here
btw: the new virtuoso-6.1.6-rc3 _does_ require a re-build of soprano-backend- virtuoso which I now also linked into that project
Nico
Why? Virtuoso isn't even installed when building soprano.
I'm talking about soprano-backend- virtuoso, not soprano
Nico
Neither with soprano or soprano-backends virtuoso isn't installed in build enviroment. You would think it needs a rebuild, but obviosly it doesn't. -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Monday 30 Jul 2012 16:17:09 hrvojes wrote:
On Monday 30 of July 2012 16:12:31 Nico Kruber wrote:
On Monday 30 Jul 2012 15:58:40 hrvojes wrote:
On Monday 30 of July 2012 12:48:45 Nico Kruber wrote:
On Monday 30 Jul 2012 11:10:04 you wrote:
On Saturday 28 Jul 2012 12:11:45 Nico Kruber wrote:
On Saturday 28 Jul 2012 09:18:21 Sven Burmeister wrote: > 1. AFAIK KDE 4.9 must not be used with virtuoso 6.1.5 but only > .4 > or > .6 > (to > be released soon [since a week or more])
I guess, we have to wait for 6.1.6 then or is there a 6.1.5 package with the according patches somewhere in OBS yet? last mail from Will about this suggested that the openSUSE patches for this are not fully correct yet
Since 6.1.6 has not been released yet and I don't know, which patch fixes this issue, I created a branch with the current development snapshot of virtuoso-6 which happens to be RC3 of 6.1.6 - see https://build.opensuse.org/package/show?package=virtuoso&project=hom e% 3A Ni co K%3Abranches%3AKDE%3ARelease%3A49
I don't know, whether we should push it to KR49 - I'm waiting for comments on this one here
btw: the new virtuoso-6.1.6-rc3 _does_ require a re-build of soprano-backend- virtuoso which I now also linked into that project
Nico
Why? Virtuoso isn't even installed when building soprano.
I'm talking about soprano-backend- virtuoso, not soprano
Nico
Neither with soprano or soprano-backends virtuoso isn't installed in build enviroment. You would think it needs a rebuild, but obviosly it doesn't.
oh, I see... I updated the virtuoso package, logged out and back in again and the soprano backend was complaining that it couldn't find out the virtuoso version, so I only guessed. After re-building and installing the soprano-backend- virtuoso, log out+in, it worked, but maybe this had something to do with the shared library still being loaded - sorry for the confusion then Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Montag, 30. Juli 2012, 11:10:04 schrieb Nico Kruber:
Since 6.1.6 has not been released yet and I don't know, which patch fixes this issue, I created a branch with the current development snapshot of virtuoso-6 which happens to be RC3 of 6.1.6 - see https://build.opensuse.org/package/show?package=virtuoso&project=home%3ANico K%3Abranches%3AKDE%3ARelease%3A49
AFAIK fedora and others do the same.
I don't know, whether we should push it to KR49 - I'm waiting for comments on this one here
Worse than a non-working nepomuk would only be a constantly crashig nepomuk. So I'd say it's worthe the risk to push an RC3 package. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dnia poniedziałek, 30 lipca 2012 15:22:09 Sven Burmeister pisze:
Worse than a non-working nepomuk would only be a constantly crashig nepomuk.
I dare disagree. A crashing nepomuk crashes, complains about it loudly and that is it, whereas a working nepomuk pwns my machine. Yours pwndly, Chris -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Montag, 30. Juli 2012, 21:19:29 schrieb Křištof Želechovski:
Worse than a non-working nepomuk would only be a constantly crashig nepomuk. I dare disagree. A crashing nepomuk crashes, complains about it loudly and
Dnia poniedziałek, 30 lipca 2012 15:22:09 Sven Burmeister pisze: that is it, whereas a working nepomuk pwns my machine.
Unless you know that one can turn it off via systemsettings Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Montag, 30. Juli 2012, 11:10:04 schrieb Nico Kruber:
Since 6.1.6 has not been released yet and I don't know, which patch fixes this issue, I created a branch with the current development snapshot of virtuoso-6 which happens to be RC3 of 6.1.6 - see https://build.opensuse.org/package/show?package=virtuoso&project=home%3ANico K%3Abranches%3AKDE%3ARelease%3A49
Did I understand correctly that it suffices to update virtuoso-server + virtuoso-drivers? If so, does dolphin show any extra infos for e.g. pictures for you using virtuoso 6.1.6 RC3 with KR49 packages? Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Tuesday 31 Jul 2012 13:20:05 Sven Burmeister wrote:
Am Montag, 30. Juli 2012, 11:10:04 schrieb Nico Kruber:
Since 6.1.6 has not been released yet and I don't know, which patch fixes this issue, I created a branch with the current development snapshot of virtuoso-6 which happens to be RC3 of 6.1.6 - see https://build.opensuse.org/package/show?package=virtuoso&project=home%3ANi co K%3Abranches%3AKDE%3ARelease%3A49
Did I understand correctly that it suffices to update virtuoso-server + virtuoso-drivers?
I thought so
If so, does dolphin show any extra infos for e.g. pictures for you using virtuoso 6.1.6 RC3 with KR49 packages?
You mean in the information panel? No, unfortunately not - nothing there... Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Am Mittwoch, 1. August 2012, 09:12:52 schrieb Nico Kruber:
If so, does dolphin show any extra infos for e.g. pictures for you using virtuoso 6.1.6 RC3 with KR49 packages?
You mean in the information panel? No, unfortunately not - nothing there...
In 4.9 you can go to "control" or however that new settings button in the toolbar is called and add extra information to be shown below the file/folder. There one should be able to select "size" e.g. for images, yet it is not possible here. http://ppenz.blogspot.de/2012/06/dolphin-21.html second screenshot I wonder whether it is something to report upstream or an openSUSE/packaging/fixed in final issue. Sven -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Wednesday 01 Aug 2012 10:39:21 Sven Burmeister wrote:
Am Mittwoch, 1. August 2012, 09:12:52 schrieb Nico Kruber:
If so, does dolphin show any extra infos for e.g. pictures for you using virtuoso 6.1.6 RC3 with KR49 packages?
You mean in the information panel? No, unfortunately not - nothing there...
In 4.9 you can go to "control" or however that new settings button in the toolbar is called and add extra information to be shown below the file/folder. There one should be able to select "size" e.g. for images, yet it is not possible here.
http://ppenz.blogspot.de/2012/06/dolphin-21.html
second screenshot
I wonder whether it is something to report upstream or an openSUSE/packaging/fixed in final issue.
Sven
nope, this doesn't seem to work for me with KR49 and virtuoso 6.1.6 final :( Nico -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Dnia wtorek, 31 lipca 2012 13:20:05 Sven Burmeister pisze:
Am Montag, 30. Juli 2012, 11:10:04 schrieb Nico Kruber:
Did I understand correctly that it suffices to update virtuoso-server + virtuoso-drivers? If so, does dolphin show any extra infos for e.g. pictures for you using virtuoso 6.1.6 RC3 with KR49 packages?
I was told metadata display in Dolphin was handled by and depended exclusively on strigi? Chris -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
Lørdag den 4. august 2012 21:13:54 Křištof Želechovski skrev:
Dnia wtorek, 31 lipca 2012 13:20:05 Sven Burmeister pisze:
Am Montag, 30. Juli 2012, 11:10:04 schrieb Nico Kruber:
Did I understand correctly that it suffices to update virtuoso-server + virtuoso-drivers? If so, does dolphin show any extra infos for e.g. pictures for you using virtuoso 6.1.6 RC3 with KR49 packages?
I was told metadata display in Dolphin was handled by and depended exclusively on strigi?
Pretty sure it only needs Nepomuk, not necessarily Strigi (the indexer). -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Saturday 04 Aug 2012 21:39:08 Martin Schlander wrote:
Lørdag den 4. august 2012 21:13:54 Křištof Želechovski skrev:
Dnia wtorek, 31 lipca 2012 13:20:05 Sven Burmeister pisze:
Am Montag, 30. Juli 2012, 11:10:04 schrieb Nico Kruber:
Did I understand correctly that it suffices to update virtuoso-server + virtuoso-drivers? If so, does dolphin show any extra infos for e.g. pictures for you using virtuoso 6.1.6 RC3 with KR49 packages?
I was told metadata display in Dolphin was handled by and depended exclusively on strigi?
Pretty sure it only needs Nepomuk, not necessarily Strigi (the indexer).
Nepomuk uses libstrigi plugins to extract the metadata, which Nepomuk stores, Dolphin queries and displays this data. Strigi is no longer used as a standalone indexer, just its plugins. Will -- Will Stephenson, openSUSE Board, Booster, KDE Developer SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (16)
-
Alin M Elena -
Anders Johansson -
Andreas Jaeger -
Basil Chupin -
Carl Fletcher -
doiggl＠velocitynet.com.au -
Felix Miata -
hrvojes -
Křištof Želechovski -
Markus -
Martin Schlander -
Nico Kruber -
Raymond Wooninck -
Sven Burmeister -
todd rme -
Will Stephenson