[opensuse] Updating to KDE SC 4.13 from KDE:Current
In the next hours KDE:Current will publish KDE 4.13 SC. As that this release comes with a big change (Nepomuk -> Baloo), we would like some simple steps in order to perform the right upgrade. Before the upgrade In order to migrate data automatically from the Nepomuk store to the new format (used by Baloo), you will need Nepomuk up and running, and just for the time needed for the migration. Ensure that Nepomuk is running before the update (in System Settings > Desktop Search). This is only necessary in case Nepomuk is in use on the system. The upgrade itself * If you are already using KDE:Current then the upgrade should be a simple "zypper up" or upgrade packages through YaST Software Management. * If you are not yet using KDE:Current, then please follow the instructions on https://en.opensuse.org/KDE_repositories#Current_KDE_SC_release on how to add the necessary repositories. After adding them, a zypper dup is required to ensure that all the KDE packages are coming from KDE:Current. Please do not remove nepomuk, as that otherwise the migration to baloo will fail !! Also after the upgrade please make sure that the following package is installed "baloo-file". After this check, log off and back on. The migrator will then run and move all the data that can be migrated to the new system. It will also turn off Nepomuk at the end of the migration. At this moment it would be safe to remove the nepomuk related packages like nepomuk-core, libnepomukwidgets, soprano*, strigi, virtuoso and shared- desktop-ontologies. There are only a few packages left that are still requiring the nepomuk-framework (like bangarang, kweshtunotes, etc). Using Baloo Unlike the 'include folders to be indexed', Baloo prefers to index everything and exclude unwanted folders explicitly. With the standard setup, Baloo will index all files and directories below the home-directory. All other filesystems are indicated as omitted. This can be changed by deleting the respective entries. Unfortunately it is not possible to switch baloo off through systemsettings. If baloo is not wanted on the system, then the package "baloo-file" needs to be removed to prevent files being indexed. The package "baloo-pim" (only present when kdepim is installed) can be removed if no search capabilities are required for kmail. The only search client currently available for baloo, is the package called milou. Milou can be placed in the panel for easy access and the usage is quite simple. The search term is indicated and search results are shown for files, emails, etc. In the Milou settings, the categories from which results are shown can be selected. Milou can NOT be placed in the systray, as that this would cause the plasma desktop to crash upon login. Tags on files are no longer stored inside the database, but stored in the extended file attributes (xattr), which are stored in separate files on the filesystem. Known issues with KDE 4.13 - The initial indexing can be heavy on I/O especially if there are large text files: either one waits till the indexing is complete (this step is done only once), or the folder containing such files is excluded using System Settings. - Some data will be lost during the migration: in particular, emails will have to be re-indexed, and file<->activity associations, if used, will not be preserved. - Milou causes the Plasma-desktop to crash if it is placed in the systray !! Regards openSUSE KDE Community Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/24/2014 1:02 PM, Raymond Wooninck wrote:
In the next hours KDE:Current will publish KDE 4.13 SC. As that this release comes with a big change (Nepomuk -> Baloo), we would like some simple steps in order to perform the right upgrade.
Sigh. Just when Nepomuk was starting to work well, imposed no significant load, and searches could be done within Dolphin, we reverse course, once again, and shitcan the whole thing for some other untried and undebugged package, with its own search engine, no integration, and with no ability for users to control it through settings. -- _____________________________________ ---This space for rent---
On 04/24/2014 05:02 PM, Raymond Wooninck wrote:
In the next hours KDE:Current will publish KDE 4.13 SC. As that this release comes with a big change (Nepomuk -> Baloo), we would like some simple steps in order to perform the right upgrade.
Before the upgrade
In order to migrate data automatically from the Nepomuk store to the new format (used by Baloo), you will need Nepomuk up and running, and just for the time needed for the migration. Ensure that Nepomuk is running before the update (in System Settings > Desktop Search). This is only necessary in case Nepomuk is in use on the system.
The upgrade itself
* If you are already using KDE:Current then the upgrade should be a simple "zypper up" or upgrade packages through YaST Software Management. * If you are not yet using KDE:Current, then please follow the instructions on https://en.opensuse.org/KDE_repositories#Current_KDE_SC_release on how to add the necessary repositories. After adding them, a zypper dup is required to ensure that all the KDE packages are coming from KDE:Current. Greetings! I just tried to perform the update, after adding KDE:Current and the extras repository, and I get the following message:
kdebase4-runtime-4.13.0-3.1.x86_64 requires kdebase4-runtime-branding = 4.13, but this requirement cannot be provided and kwin-4.11.8-9.1.x86_64 requires kdebase4-workspace-branding = 4.13, but this requirement cannot be provided I include the full conflicts file as an attachment (I usually disregard the dependency conflict with K3b since I do not use it). I am also attaching the list of my repositories (zypper lr -u) What am I doing worng? Thanks in advance! -- Pablo M. Dotro pdotro@df.uba.ar Laboratorio de Ondas y Termodinámica Departamento de Física (FCEyN - UBA)
On 4/24/2014 3:37 PM, Pablo Dotro wrote:
Greetings! I just tried to perform the update, after adding KDE:Current and the extras repository, and I get the following message:
kdebase4-runtime-4.13.0-3.1.x86_64 requires kdebase4-runtime-branding = 4.13, but this requirement cannot be provided
and
kwin-4.11.8-9.1.x86_64 requires kdebase4-workspace-branding = 4.13, but this requirement cannot be provided
I include the full conflicts file as an attachment (I usually disregard the dependency conflict with K3b since I do not use it). I am also attaching the list of my repositories (zypper lr -u) What am I doing worng? Thanks in advance!
Generally when the packages are only the brandings you can choose the "break by ignoring dependencies, because all these are is some of the icons, logos and splash screens specific to opensuse etc. Usually purely cosmetic and if missing some other generic versions will be used. Still, I always hesitate to recommend BREAK option, and you might give them a day or two to clean up these issues, or file a bug report. It always amazes me that this kind of dependency problem creeps in with almost every new release and nobody notices till the users try it out. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thursday 24 of April 2014 19:37:21 Pablo Dotro wrote: ....
I include the full conflicts file as an attachment (I usually disregard the dependency conflict with K3b since I do not use it). I am also attaching the list of my repositories (zypper lr -u) What am I doing worng? Thanks in advance!
Correct solution is to downgrade the branding packages. Cheers, Hrvoje
On 25/04/14 06:02, Raymond Wooninck wrote:
In the next hours KDE:Current will publish KDE 4.13 SC. As that this release comes with a big change (Nepomuk -> Baloo), we would like some simple steps in order to perform the right upgrade.
[pruned] Thank you Raymond. The upgrade went smoothly - once I chose to downgrade a couple of openSUSE-branding files. This openSUSE-branding dependency rejection of an upgrade must be hell for 'newbies' who try and do an upgrade :- . If simply downgrading the *-branding file(s) to get a satisfactory result then it means that this dependency is worthless and therefore can be done away with, right? So why not either get this dependency sorted out before a new release is 'allowed to fly' or simply just get rid of the check for this? BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Basil Chupin wrote:
The upgrade went smoothly - once I chose to downgrade a couple of openSUSE-branding files.
This openSUSE-branding dependency rejection of an upgrade must be hell for 'newbies' who try and do an upgrade :- .
Well, Strangely enough the openSUSE branding files were not touched by the KDE 4.13 upgrade. They were initially copied from the KDE:Release:412 repository and then newly build for KDE:Current. Since that moment they were not updated. So I guess that people running into this issue, didn't downgrade the branding files when they switched to the new KDE:Current repository.
If simply downgrading the *-branding file(s) to get a satisfactory result then it means that this dependency is worthless and therefore can be done away with, right?
So why not either get this dependency sorted out before a new release is 'allowed to fly' or simply just get rid of the check for this?
This is already sorted out and the branding files are left as they were on the official openSUSE release. So people running 12.3, will still see the 12.3 branding for KDE, etc. However with the creation of each new repository, these branding files need to be rebuild once. After that they are static and do not need any updates. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Friday, April 25, 2014 07:49:14 PM Raymond Wooninck wrote:
Basil Chupin wrote:
The upgrade went smoothly - once I chose to downgrade a couple of openSUSE-branding files.
This openSUSE-branding dependency rejection of an upgrade must be hell for 'newbies' who try and do an upgrade :- .
Well, Strangely enough the openSUSE branding files were not touched by the KDE 4.13 upgrade. They were initially copied from the KDE:Release:412 repository and then newly build for KDE:Current. Since that moment they were not updated.
So I guess that people running into this issue, didn't downgrade the branding files when they switched to the new KDE:Current repository.
If simply downgrading the *-branding file(s) to get a satisfactory result then it means that this dependency is worthless and therefore can be done away with, right?
So why not either get this dependency sorted out before a new release is 'allowed to fly' or simply just get rid of the check for this? This is already sorted out and the branding files are left as they were on the official openSUSE release. So people running 12.3, will still see the 12.3 branding for KDE, etc. However with the creation of each new repository, these branding files need to be rebuild once. After that they are static and do not need any updates.
I just updated. Only issues I had were milou was not selected in: http://download.opensuse.org/repositories/KDE:/Extra/ KDE_Current_openSUSE_13.1/ I selected it before install. Baloo-file was already selected and installed fine. Only other problem is with K3B and Amarok from Packman. My mail, contacts, newsreader mail all seem to have migrated fine. None missing that I can see. Will post more as I if I find and issues or solutions. -- openSUSE 13.1(Linux 3.11.10-7-desktop x86_64| Intel(R) Quad Core(TM) i5-4440 CPU @ 3.10GHz|8GB DDR3| GeForce 8400GS (NVIDIA-Linux-x86_64-331.49)|KDE 4.12.4 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/25/2014 3:14 PM, upscope wrote:
My mail, contacts, newsreader mail all seem to have migrated fine. None missing that I can see.
Why would they not? All of those things are sitting in the same files they were before. Its not like this was a complete OS replacement. The changes are very small. It turns out that Milou is not worth installing, because it does not report content results from all files. It is really rather limited. It The good news is that the search capability in Dolphin does work, in spite of Raymond reporting that the only search agent was Milou. And you can make it search either file content or file names. Lost were all the file tags. I use this feature while maintaining code to tag files that need attention for certain reasons, and all the reasons (tags) were lost, and all the files with tags no longer are tagged. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/14 08:43, John Andersen wrote:
My mail, contacts, newsreader mail all seem to have migrated fine. None missing that I can see. Why would they not? All of those things are sitting in the same files
On 4/25/2014 3:14 PM, upscope wrote: they were before. Its not like this was a complete OS replacement. The changes are very small.
It turns out that Milou is not worth installing, because it does not report content results from all files. It is really rather limited. It
The good news is that the search capability in Dolphin does work, in spite of Raymond reporting that the only search agent was Milou. And you can make it search either file content or file names.
I am 'confus-ed'. I tried a few minutes ago to do a search for contents using Dolphin (because the other thing - Sweet Babboo, whatever, didn't even bother to pass wind - and while the search options in Dolphin now seem to be better presented (?or changed), Dolphin couldn't find its own shadow let alone what I was asking to be found :-( . For my money, the *only* search facility worth anything is the one in Midnight Commander (mc).
Lost were all the file tags. I use this feature while maintaining code to tag files that need attention for certain reasons, and all the reasons (tags) were lost, and all the files with tags no longer are tagged.
BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 26 of April 2014 16:53:21 Basil Chupin wrote:
For my money, the *only* search facility worth anything is the one in Midnight Commander (mc).
Have you tried recoll? I've had no problems with it so far.
BC
-- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/14 16:58, auxsvr@gmail.com wrote:
On Saturday 26 of April 2014 16:53:21 Basil Chupin wrote:
For my money, the *only* search facility worth anything is the one in Midnight Commander (mc). Have you tried recoll? I've had no problems with it so far.
I don't see 'recoll' in YaST's list of files. On top of that, I see no reason to add more bloatware when a program like mc is like a Swiss knife of file managers. But, of course, 'horses for courses' and so on and etc. And why not, I ask, as long as someone is having fun coding the stuff and trying to reinvent a better round wheel......... BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[26.04.2014 09:10] [Basil Chupin]:
On 26/04/14 16:58, auxsvr@gmail.com wrote:
On Saturday 26 of April 2014 16:53:21 Basil Chupin wrote:
For my money, the *only* search facility worth anything is the one in Midnight Commander (mc). Have you tried recoll? I've had no problems with it so far.
I don't see 'recoll' in YaST's list of files.
It is in the KDE:Extra repository, like milou is. HTH, Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/26/2014 09:39 AM, Werner Flamme wrote:
[26.04.2014 09:10] [Basil Chupin]:
On 26/04/14 16:58, auxsvr@gmail.com wrote:
On Saturday 26 of April 2014 16:53:21 Basil Chupin wrote:
For my money, the *only* search facility worth anything is the one in Midnight Commander (mc). Have you tried recoll? I've had no problems with it so far.
I don't see 'recoll' in YaST's list of files.
It is in the KDE:Extra repository, like milou is.
HTH, Werner
Wait, Recoll doesn't use either nepomuk or balou, nor does the one in midnight commander. These things appear to launch a torrent of disk activity digging through files looking for something each time you query something. This is great if you have exactly 13 files. I've got gigabytes of code, linker output, etc. Who has time to wait for that process each time you search? Milou, limited as it is, is better than that. And the search facility built into Dolphin is even better. I need to find out every code module that references a specific data element when restructuring data structures. I need to see every line of code that reads or updates that data element. nepomuk or balou allows you to find each such reference in seconds, not minutes. It appears those other tools are hold-overs from another century. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday 26 of April 2014 09:58:24 John Andersen wrote:
Wait, Recoll doesn't use either nepomuk or balou, nor does the one in midnight commander.
These things appear to launch a torrent of disk activity digging through files looking for something each time you query something. This is great if you have exactly 13 files.
I've got gigabytes of code, linker output, etc. Who has time to wait for that process each time you search?
I have gigabytes of documents, PDF, text, doc, tex etc and recoll finds keywords using an excellent query language within seconds after the initial indexing.
Milou, limited as it is, is better than that. And the search facility built into Dolphin is even better.
My experience with baloo so far is that it is more resource-intensive than recoll. Perhaps this will improve in the future. Also, recoll allows you to schedule filesystem indexing during off-hours, so that it can be the least intrusive of all, if you want.
I need to find out every code module that references a specific data element when restructuring data structures. I need to see every line of code that reads or updates that data element.
nepomuk or balou allows you to find each such reference in seconds, not minutes.
It appears those other tools are hold-overs from another century.
I would prefer nepomuk, if it weren't so buggy as to be close to useless. Baloo and the accompanying technologies seem to be a step in the right direction and can be used for more than just filesystem indexing. I hope they will replace recoll here after they stabilize more, but for now recoll is very close to perfect. -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/04/14 02:39, Werner Flamme wrote:
[26.04.2014 09:10] [Basil Chupin]:
On 26/04/14 16:58, auxsvr@gmail.com wrote:
On Saturday 26 of April 2014 16:53:21 Basil Chupin wrote:
For my money, the *only* search facility worth anything is the one in Midnight Commander (mc). Have you tried recoll? I've had no problems with it so far. I don't see 'recoll' in YaST's list of files. It is in the KDE:Extra repository, like milou is.
HTH, Werner
Thank you. BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen wrote:
It turns out that Milou is not worth installing, because it does not report content results from all files. It is really rather limited.
At this moment Milou reports back 10 hits for each category that is selected. I agree with you that this is a rather limited functionality and unfortunately there is no way to increase the number of results. In my honest opinion, the best search client for file content is still Recoll.
The good news is that the search capability in Dolphin does work, in spite of Raymond reporting that the only search agent was Milou. And you can make it search either file content or file names.
Dolphin offers the capability to search in file names or file content. Kmail offers the capability to search in emails The only client/agent that offers an integrated search is Milou. I guess that I should have stated a little different in my original email.
Lost were all the file tags. I use this feature while maintaining code to tag files that need attention for certain reasons, and all the reasons (tags) were lost, and all the files with tags no longer are tagged.
Tags are no longer stored within the Baloo database. Tags are now stored in the Extended Attributes, which in their turn are stored on the filesystem. Depending on the view, this is good or bad. Extended Attributes can be copied together with the file, so tags will no longer be lost when the file is copied (if the target filesystem supports extended attributes). On the bad side, maybe people do not want that these tags are being copied. There were discussions upstream that Dolphin would copy the extended attributes automatically whenever a file is being copied, but I am not sure if this got implemented. Raymond -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 26 Apr 2014 09:47:12 Raymond Wooninck wrote:
At this moment Milou reports back 10 hits for each category that is selected. I agree with you that this is a rather limited functionality and unfortunately there is no way to increase the number of results.
In my honest opinion, the best search client for file content is still Recoll.
Raymond, Is it absolutely necessary to upgrade to Baloo from Nepomuk for 4.13? If I don't install Baloo, will Nepomuk stop working? Will search not work in 4.13 apps (Dolphin, Kmail etc) without Baloo? -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Rodney Baker wrote:
Is it absolutely necessary to upgrade to Baloo from Nepomuk for 4.13? If I don't install Baloo, will Nepomuk stop working? Will search not work in 4.13 apps (Dolphin, Kmail etc) without Baloo?
Rodney, I am afraid that you do not have a choice. Of course you remove some of the baloo packages and keep Nepomuk installed. However dolphin, kmail, etc will not perform any searches without baloo. KDE 4.13 is Nepomuk free (so to speak) and instead is now depending on Baloo. So if you do not want Baloo, then you should NOT upgrade to 4.13 but stay on a lower version. Regards Raymond -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/04/14 06:06, Raymond Wooninck wrote:
Rodney Baker wrote:
Is it absolutely necessary to upgrade to Baloo from Nepomuk for 4.13? If I don't install Baloo, will Nepomuk stop working? Will search not work in 4.13 apps (Dolphin, Kmail etc) without Baloo? Rodney,
I am afraid that you do not have a choice. Of course you remove some of the baloo packages and keep Nepomuk installed. However dolphin, kmail, etc will not perform any searches without baloo. KDE 4.13 is Nepomuk free (so to speak) and instead is now depending on Baloo.
So if you do not want Baloo, then you should NOT upgrade to 4.13 but stay on a lower version.
Regards
Raymond
Sorry to sound dense, but what is there all this talk about 'Baboo' and 'Mildew' - or whatever the names are? WHICH is the search engine which came with KDE 4.13? I understand that it was 'Baboo' and it replaced Nepopuke, right? So where does this 'Mildew' which ahs been mentioned many times now come into it? :-) BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
It's not baboo, it's badpoo. On Sun, Apr 27, 2014 at 12:33 AM, Basil Chupin <blchupin@iinet.net.au> wrote:
On 27/04/14 06:06, Raymond Wooninck wrote:
Rodney Baker wrote:
Is it absolutely necessary to upgrade to Baloo from Nepomuk for 4.13? If I don't install Baloo, will Nepomuk stop working? Will search not work in 4.13 apps (Dolphin, Kmail etc) without Baloo?
Rodney,
I am afraid that you do not have a choice. Of course you remove some of the baloo packages and keep Nepomuk installed. However dolphin, kmail, etc will not perform any searches without baloo. KDE 4.13 is Nepomuk free (so to speak) and instead is now depending on Baloo.
So if you do not want Baloo, then you should NOT upgrade to 4.13 but stay on a lower version.
Regards
Raymond
Sorry to sound dense, but what is there all this talk about 'Baboo' and 'Mildew' - or whatever the names are?
WHICH is the search engine which came with KDE 4.13? I understand that it was 'Baboo' and it replaced Nepopuke, right? So where does this 'Mildew' which ahs been mentioned many times now come into it? :-)
BC
-- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/04/14 17:35, Lars Kruczynski wrote:
It's not baboo, it's badpoo.
Sounds more like hullabaloo from the comments flowing in. Or as John's attachment shows, "Not this s*** again!". [pruned] BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/27/2014 12:51 AM, Basil Chupin wrote:
On 27/04/14 17:35, Lars Kruczynski wrote:
It's not baboo, it's badpoo.
Sounds more like hullabaloo from the comments flowing in.
Or as John's attachment shows, "Not this s*** again!".
[pruned]
BC
My comments referred to the FORCED MARCH, a massive change with zero advance warning (KDE's fault) and no way of integrating it into yast (opensuse's fault). My tests prove, to my satisfaction, that things are working as well or better than Nepomuk (which for me, on this modest hardware, was VERY well, finally). So 1) I have to give Kudos to KDE for the smooth conversion. 2) I have to give the raspberry to KDE for not a shred of documentation and the highhanded way this was foisted on the userbase (we should be used to this from KDE by now but it still stinks). 3)I have to give the rasberry to opensuse for not integrating it into yast 4)And I have give the WTF to those people reporting HUGE CPU and Disk load when running certain processes, and suggest, they might want to figure out what those file-types are that are causing such fits, and add them to the exclusion list in baloofilerc -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
John Andersen wrote:
My comments referred to the FORCED MARCH, a massive change with zero advance warning (KDE's fault) and no way of integrating it into yast (opensuse's fault).
Can I comment here a WTF ?? What do you want to integrate into YaST ? Raymond -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
The ability to turn it off and on, select directories to include/exclude, and file types to exclude. In short, All of those things that you could do for managing nepomuck. Since all of this ends up being a manipulation of one's baloofilerc (something I had to find by trial and error and an hour of googling) it shouldn't have been doable, and would have gone a long way toward user acceptance. Oh, and I would have set indexing OFF by default too, which is the same way that opensuse delivered nepomuck IIRC. On April 28, 2014 1:26:27 AM PDT, Raymond Wooninck <tittiatcoke@gmail.com> wrote:
John Andersen wrote:
My comments referred to the FORCED MARCH, a massive change with zero advance warning (KDE's fault) and no way of integrating it into yast (opensuse's fault).
Can I comment here a WTF ?? What do you want to integrate into YaST ?
Raymond -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/28/2014 11:42 AM, John Andersen wrote:
The ability to turn it off and on, select directories to include/exclude, and file types to exclude.
In short, All of those things that you could do for managing nepomuck.
Since all of this ends up being a manipulation of one's baloofilerc (something I had to find by trial and error and an hour of googling) it shouldn't have been doable, and would have gone a long way toward user acceptance.
Oh, and I would have set indexing OFF by default too, which is the same way that opensuse delivered nepomuck IIRC.
Three's an old joke about a boy who said nothing from birth until one day he complained at a mean that him mashed potatoes were lumpy. His parents were amazed to hear him speak. His comment "Well I didn't say any8tng because until now everything was OK". I realise many other people are complaining about this release of KDE, but we are used to them complaining. There seems to be a visceral, a religious reaction to me complaining (and it wasn't even in my signature block!). Until now I've been a keen supporter of KDE. Even in .0, .1, .2 days when it had new release teething troubles, rather than complain I pointed out that this was a normal cycle of new product with FSS. But now we had a stable and mature product at .11, .12. Control of nepomuk was in systemsettings and as John said, it default was OFF so we could ignore it if we installed it unaware. And anyway, it wouldn't do anything unless it was configured and configuring it involved telling it which directories to index. I don't think I'm being unfair when I use the term "Jump the shark" for the side effects we are experiencing with this new release. The last few releases went pretty smoothly, now this! Perhaps the emotional reaction is because we've grown used to KDE being stable, not giving us any surprises, not causing loss of data, not doing a volte-face in how it works. John and I usually disagree on so much, but I agree with him in this instance. -- "Excellence is the gradual result of always striving to do better." -- Pat Riley -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/28/2014 8:42 AM, John Andersen wrote:
Since all of this ends up being a manipulation of one's baloofilerc (something I had to find by trial and error and an hour of googling) it shouldn't have been doable, and would have gone a long way toward user acceptance.
FOLLOWUP... Meant to say "should have" been doable. (Sorry, typing on a smartphone at the time). If I knew ruby (or whatever Yast is written in this week) I would have tried to hack the prior nepomuck yast handler to deal with the new baloofilerc. But, believe me, you don't want me hacking around in Yast. This being said, I have to report that *the cut over went fine for me*, because my nepomuck settings were faithfully copied over (and nepomuck was working fine for me previously). These old settings were already excluding some huge vmware directories, torrents, etc. So it seems those people who had taken the time to get Nepomuck working intelligently and had built in a proper set of exclusions were the *least* impacted by this changeover. And those who didn't use nepomuck or didn't ever adjust its settings got hammered the most. Dopeslap the newbie seem to be the name of the game. *You will have problems with Baloo if you:* 1)Mount things in your home directory tree 2)Do not exclude huge files not on the normal exclusion list inf baloofilerc 3)Do not exclude directories containing files that are opened and closed frequently and which are also huge and are binary. (Torrents are appended to and closed frequently as a crash protection mechanism, and they are binary and they are huge, and their extensions can't be relied upon. Other than these common oversights, I haven't noticed any performance penalties *even* when creating huge numbers of changes in indexed directories by recompiling entire subsystems. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/28/2014 01:13 PM, John Andersen pecked at the keyboard and wrote:
On 4/28/2014 8:42 AM, John Andersen wrote:
Since all of this ends up being a manipulation of one's baloofilerc (something I had to find by trial and error and an hour of googling) it shouldn't have been doable, and would have gone a long way toward user acceptance.
FOLLOWUP...
Meant to say "should have" been doable. (Sorry, typing on a smartphone at the time).
If I knew ruby (or whatever Yast is written in this week) I would have tried to hack the prior nepomuck yast handler to deal with the new baloofilerc.
But, believe me, you don't want me hacking around in Yast.
This being said, I have to report that *the cut over went fine for me*, because my nepomuck settings were faithfully copied over (and nepomuck was working fine for me previously). These old settings were already excluding some huge vmware directories, torrents, etc.
So it seems those people who had taken the time to get Nepomuck working intelligently and had built in a proper set of exclusions were the *least* impacted by this changeover.
And those who didn't use nepomuck or didn't ever adjust its settings got hammered the most. Dopeslap the newbie seem to be the name of the game.
*You will have problems with Baloo if you:* 1)Mount things in your home directory tree 2)Do not exclude huge files not on the normal exclusion list inf baloofilerc 3)Do not exclude directories containing files that are opened and closed frequently and which are also huge and are binary. (Torrents are appended to and closed frequently as a crash protection mechanism, and they are binary and they are huge, and their extensions can't be relied upon.
Other than these common oversights, I haven't noticed any performance penalties *even* when creating huge numbers of changes in indexed directories by recompiling entire subsystems.
Then there are some of us that just plain do not want Big Brother looking over our shoulder or being able to watch the tape at a later time. Hopefully I have managed to turn off baloo for good. What ever happened to the good old days when we (end users) were the ones that decided what software to install on top of the DE. Now it seems that everything is getting so intertwined you cannot delete a package without it f**king up the install. I guess it's time to start looking at another DE. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/28/2014 10:43 AM, Ken Schneider - openSUSE wrote:
Then there are some of us that just plain do not want Big Brother looking over our shoulder or being able to watch the tape at a later time. Hopefully I have managed to turn off baloo for good. What ever happened to the good old days when we (end users) were the ones that decided what software to install on top of the DE. Now it seems that everything is getting so intertwined you cannot delete a package without it f**king up the install. I guess it's time to start looking at another DE.
I agree with these sentiments, although a searchable index on one's own machine is hardly big brother. The actual executables and libraries of Baloo wouldn't be a problem if they had just made a proper Configure desktop plug in *and* made it Opt IN. After all, there are lots of parts of KDE that are intertwined thusly, and which cause no problems simply by being installed, because their use is not mandatory. Why is THIS tail allowed to wag the entire KDE dog? -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/28/2014 01:54 PM, John Andersen pecked at the keyboard and wrote:
On 4/28/2014 10:43 AM, Ken Schneider - openSUSE wrote:
Then there are some of us that just plain do not want Big Brother looking over our shoulder or being able to watch the tape at a later time. Hopefully I have managed to turn off baloo for good. What ever happened to the good old days when we (end users) were the ones that decided what software to install on top of the DE. Now it seems that everything is getting so intertwined you cannot delete a package without it f**king up the install. I guess it's time to start looking at another DE.
I agree with these sentiments, although a searchable index on one's own machine is hardly big brother.
It might be if you don't what is going on under the hood. Are you sure there is no code to phone home with the results? Just saying. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 4/28/2014 3:38 PM, Ken Schneider - openSUSE wrote:
It might be if you don't what is going on under the hood. Are you sure there is no code to phone home with the results?
Just saying.
Haven't read the code yet. Have looked at Netstat, and see no unexplained connections. While we are on the subect -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 26 Apr 2014 13:06:59 Raymond Wooninck wrote:
Rodney Baker wrote:
Is it absolutely necessary to upgrade to Baloo from Nepomuk for 4.13? If I don't install Baloo, will Nepomuk stop working? Will search not work in 4.13 apps (Dolphin, Kmail etc) without Baloo?
Rodney,
I am afraid that you do not have a choice. Of course you remove some of the baloo packages and keep Nepomuk installed. However dolphin, kmail, etc will not perform any searches without baloo. KDE 4.13 is Nepomuk free (so to speak) and instead is now depending on Baloo.
So if you do not want Baloo, then you should NOT upgrade to 4.13 but stay on a lower version.
Regards
Raymond
Thanks - I assumed that was the case but assumptions can be dangerous. :) Since Nepomuk actually seems to be working well for me at the moment I think I'll stay put on 4.12 until Baloo is a little more mature. Nepomuk took several generations before it was actually stable and useful without bring the system to a screaming crawl - I suspect Baloo will be the same. I don't think I'll bother upgrading until there are at least appropriate gui- based tools to manage it (not that I'm afraid of the command line, but when it is a fundamental building block of the desktop environment there should be a proper tool to manage it). BTW, I'm assuming that it will now be impossible to upgrade a 12.3 machine to 13.1 with KDE 4.12, since there is only now KDE Current and it has 4.13? Or is there still a base repo with KDE 4.12? Regards, Rodney. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sun, 27 Apr 2014 22:59:40 Rodney Baker wrote:
[...] BTW, I'm assuming that it will now be impossible to upgrade a 12.3 machine to 13.1 with KDE 4.12, since there is only now KDE Current and it has 4.13? Or is there still a base repo with KDE 4.12?
Replying to my own questioning after checking, it seems we now have the ridiculous situation that I have a laptop with oS 12.3/KDE 4.12.3 but if I want to upgrade it to oS 13.1 without KDE 4.13.0 I have no choice but to downgrade to KDE 4.11. Somebody didn't think too carefully about the (perhaps unintended) side effects of moving to KDE Current and (silently) dropping the previous (working) version, did they? -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/27/2014 09:45 AM, Rodney Baker wrote:
On Sun, 27 Apr 2014 22:59:40 Rodney Baker wrote:
[...] BTW, I'm assuming that it will now be impossible to upgrade a 12.3 machine to 13.1 with KDE 4.12, since there is only now KDE Current and it has 4.13? Or is there still a base repo with KDE 4.12?
Replying to my own questioning after checking, it seems we now have the ridiculous situation that I have a laptop with oS 12.3/KDE 4.12.3 but if I want to upgrade it to oS 13.1 without KDE 4.13.0 I have no choice but to downgrade to KDE 4.11.
Somebody didn't think too carefully about the (perhaps unintended) side effects of moving to KDE Current and (silently) dropping the previous (working) version, did they?
Well, it wasn't Silently dropped, it was fully Pre-announced. Further, In my tests Baloo does not induce any more cpu load or disk thrashing than Nepomuck did. Much Less, actually. I just compiled an entire subsystem, in a virtual machine which uses files located on a baloo indexed disk. It writes compile listings and link maps to that disk. And it also writes to the vmware virtual disk image in my home directory. So it was the worst possible case, a large VMWARE disk image being updated, and a multitude of files being writen, overwritten, and deleted in indexed locations. All the while I was watching baloo in Ksystemguard. It never jumped over 2 percent and never stayed there for more than an instant. The exclusions list in baloofilerc were properly excluded from being indexed. The directories on the data storage drive were properly indexed and immediately searchable for changes that I made. All of this with no disk thrashing, or high CPU load. So if you are seeing massive IO, something is broken, or misconfiguration. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/14 03:49, Raymond Wooninck wrote:
Basil Chupin wrote:
The upgrade went smoothly - once I chose to downgrade a couple of openSUSE-branding files.
This openSUSE-branding dependency rejection of an upgrade must be hell for 'newbies' who try and do an upgrade :- . Well, Strangely enough the openSUSE branding files were not touched by the KDE 4.13 upgrade. They were initially copied from the KDE:Release:412 repository and then newly build for KDE:Current. Since that moment they were not updated.
So I guess that people running into this issue, didn't downgrade the branding files when they switched to the new KDE:Current repository.
Ce`? I saw no dependency problems when I switched over to Current. Aaw, I know, you're making this up as you go along, right? :-D
If simply downgrading the *-branding file(s) to get a satisfactory result then it means that this dependency is worthless and therefore can be done away with, right?
So why not either get this dependency sorted out before a new release is 'allowed to fly' or simply just get rid of the check for this? This is already sorted out and the branding files are left as they were on the official openSUSE release. So people running 12.3, will still see the 12.3 branding for KDE, etc. However with the creation of each new repository, these branding files need to be rebuild once. After that they are static and do not need any updates.
Great. And thanks for the quick response. BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hi, My upgrading to KDE-4.13 from KDE:Current went smooth. Everything got migrated, except for KNotes. Notes did not get migrated. No way found till now (I mean googling) to migrate (or to read) the existing notes.ics from ~/.kde4/share/apps/knotes folder. Thanks Suse/kde developers for making this update otherwise so pleasureful. Regards & wishes, Rajesh -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday 27 Apr 2014 16:39:28 CA G Rajesh wrote:
Hi, My upgrading to KDE-4.13 from KDE:Current went smooth. Everything got migrated, except for KNotes. Notes did not get migrated. No way found till now (I mean googling) to migrate (or to read) the existing notes.ics from ~/.kde4/share/apps/knotes folder. Thanks Suse/kde developers for making this update otherwise so pleasureful. Regards & wishes, Rajesh
Does that mean you have found a way to get them included in Kontact? My notes didn't get migrated either. regards Ian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
ianseeks wrote: > Does that mean you have found a way to get them included in Kontact? My > notes didn't get migrated either. Yes, it's already within Kontact - I didn't do anything special to get it included. Perhaps, did you check Kontact>Settings>Configure Kontact? Whether notes/jots are selected in summary? My suggestions to the ones who haven't migrated yet to 4.13 are: 1. Either create a folder/page 'collections' in KJots, before migration (it seems to work for some) 2. Or, manually copy/paste knotes' items into KJots before migration (because notes.ics file cannot be opened later) Regards, Rajesh -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday 28 Apr 2014 07:52:01 CA G Rajesh wrote:
ianseeks wrote:
Does that mean you have found a way to get them included in Kontact? My notes didn't get migrated either.
Yes, it's already within Kontact - I didn't do anything special to get it included. Perhaps, did you check Kontact>Settings>Configure Kontact? Whether notes/jots are selected in summary? My suggestions to the ones who haven't migrated yet to 4.13 are: 1. Either create a folder/page 'collections' in KJots, before migration (it seems to work for some) 2. Or, manually copy/paste knotes' items into KJots before migration (because notes.ics file cannot be opened later) Regards, Rajesh
THanks Rajesh, seems there is a fix being released today in KDE:Current. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Monday, April 28, 2014 01:39:46 PM ianseeks wrote:
On Monday 28 Apr 2014 07:52:01 CA G Rajesh wrote:
ianseeks wrote:
Does that mean you have found a way to get them included in Kontact? My notes didn't get migrated either.
Yes, it's already within Kontact - I didn't do anything special to get it included. Perhaps, did you check Kontact>Settings>Configure Kontact? Whether notes/jots are selected in summary? My suggestions to the ones who haven't migrated yet to 4.13 are: 1. Either create a folder/page 'collections' in KJots, before migration (it seems to work for some) 2. Or, manually copy/paste knotes' items into KJots before migration (because notes.ics file cannot be opened later) Regards, Rajesh
THanks Rajesh, seems there is a fix being released today in KDE:Current.
Recent updates on KDE:Current fixed KNotes migration and other bugs. Hopefully useful. R.Chung -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/28/2014 02:33 PM, Ricardo Chung wrote:
Recent updates on KDE:Current fixed KNotes migration and other bugs.
Hopefully useful.
+1 Thank you. -- Given a choice between patching Windows and breeding cats, I'll take breeding cats. The scars heal and you feel like you're doing something productive and the kittens are so cute an sweet. You can't say any of that about patching Windows. And end users aren't as sweet an cuddly as kittens. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/04/14 21:02, Raymond Wooninck wrote:
The only search client currently available for baloo, is the package called milou. Milou can be placed in the panel for easy access and the usage is quite simple. The search term is indicated and search results are shown for files, emails, etc. In the Milou settings, the categories from which results are shown can be selected. Milou can NOT be placed in the systray, as that this would cause the plasma desktop to crash upon login.
Which repository is milou in? It didn't get installed by default :~> which milou which: no milou in (/home/bob/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/home/bob/Leo-4.11:/home/bob/bin:/home/bob/Leo-4.11-final:/home/bob/Leo-4.11) and isn't in the KDE:Current repo :~> sudo zypper in milou root's password: Loading repository data... Reading installed packages... 'milou' not found in package names. Trying capabilities. No provider of 'milou' found. Resolving package dependencies... Nothing to do. There's no point in indexing everything if you can't search the database :-( Bob - -- Bob Williams System: Linux 3.11.10-7-desktop Distro: openSUSE 13.1 (x86_64) with KDE Development Platform: 4.12.4 Uptime: 06:00am up 12 days 18:13, 4 users, load average: 0.12, 0.08, 0.06 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlNaO18ACgkQ0Sr7eZJrmU6b0QCgn6Rmr3UBAetW17yvzTrinxkU PvEAoKpJMjKPjZfWnnKtkH2FCEYzPJRZ =amIN -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 25/04/14 11:39, Bob Williams wrote:
On 24/04/14 21:02, Raymond Wooninck wrote:
The only search client currently available for baloo, is the package called milou. Milou can be placed in the panel for easy access and the usage is quite simple. The search term is indicated and search results are shown for files, emails, etc. In the Milou settings, the categories from which results are shown can be selected. Milou can NOT be placed in the systray, as that this would cause the plasma desktop to crash upon login.
Which repository is milou in? It didn't get installed by default
Found it in KDE-Extra <http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_openSUSE_13.1/> :-) Bob - -- Bob Williams System: Linux 3.11.10-7-desktop Distro: openSUSE 13.1 (x86_64) with KDE Development Platform: 4.12.4 Uptime: 06:00am up 12 days 18:13, 4 users, load average: 0.12, 0.08, 0.06 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlNaQA0ACgkQ0Sr7eZJrmU4gLQCeJpCMYqAASBAwEJJctJX9FuWJ xT4AoJU3sWg+7jGXWGTWEjHDQfVZ+NCv =nXJ3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/04/14 20:59, Bob Williams wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 25/04/14 11:39, Bob Williams wrote:
On 24/04/14 21:02, Raymond Wooninck wrote:
The only search client currently available for baloo, is the package called milou. Milou can be placed in the panel for easy access and the usage is quite simple. The search term is indicated and search results are shown for files, emails, etc. In the Milou settings, the categories from which results are shown can be selected. Milou can NOT be placed in the systray, as that this would cause the plasma desktop to crash upon login. Which repository is milou in? It didn't get installed by default
Found it in KDE-Extra <http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_openSUSE_13.1/>
:-)
Bob
HOLD IT! Weren't we told that this KDE/Extra repo is now deprecated and everything is in KDE:/Current? Or did I get the story wrong? BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Basil Chupin wrote:
HOLD IT!
Weren't we told that this KDE/Extra repo is now deprecated and everything is in KDE:/Current?
Or did I get the story wrong?
I guess that you are the one that making things up as you go along. It was never indicated that KDE:Extra would be deprecated. If you took the time to check the KDE Repository wiki on http://en.opensuse.org/SDB:KDE_repositories then you would have seen that KDE:Extra is still there. I am not trying to recreate a KDE-Tumbleweed here. KDE:Current replaces all the previous KDE:Release:XY repo's and therefore offers the complete KDE SC packages. All the other packages, add-ons, etc are still delivered through the normal repository KDE:Extra. Raymond -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Saturday, April 26, 2014 09:34:30 AM Raymond Wooninck wrote:
Basil Chupin wrote:
HOLD IT!
Weren't we told that this KDE/Extra repo is now deprecated and everything is in KDE:/Current?
Or did I get the story wrong?
I guess that you are the one that making things up as you go along. It was never indicated that KDE:Extra would be deprecated. If you took the time to check the KDE Repository wiki on http://en.opensuse.org/SDB:KDE_repositories then you would have seen that KDE:Extra is still there.
I am not trying to recreate a KDE-Tumbleweed here. KDE:Current replaces all the previous KDE:Release:XY repo's and therefore offers the complete KDE SC packages. All the other packages, add-ons, etc are still delivered through the normal repository KDE:Extra.
Raymond Did I use the wrong extra repo on my upgrade. I used:
Code: ---------- http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_openSUSE_13... ---------- Thanks Russ -- openSUSE 13.1(Linux 3.11.10-7-desktop x86_64| Intel(R) Quad Core(TM) i5-4440 CPU @ 3.10GHz|8GB DDR3| GeForce 8400GS (NVIDIA-Linux-x86_64-331.67)|KDE 4.13.0 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
upscope wrote:
Did I use the wrong extra repo on my upgrade. I used:
Code: ----------
http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_openSUSE_13... If you are running an openSUSE 13.1 system and have the KDE:Current repository enabled, then the above link is the right one to find additional KDE/Qt packages/applications. Regards Raymond -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 27/04/14 06:08, Raymond Wooninck wrote:
upscope wrote:
Did I use the wrong extra repo on my upgrade. I used:
Code: ----------
http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_openSUSE_13...
If you are running an openSUSE 13.1 system and have the KDE:Current repository enabled, then the above link is the right one to find additional KDE/Qt packages/applications.
Regards
Raymond
Oh sweet jesus! What you are saying is that the KDE:/Extra repository which shows up in YaST has been deprecated and is now replaced by KDE:/Extra/KDE_Current_openSUSE_13.1? Which is what I was querying in my earlier post that the *standard* KDE/Extra listed in YaST has disappeared. (Why hasn't there been an amendment to YaST to reflect this change?) BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
[27.04.2014 09:46] [Basil Chupin]:
On 27/04/14 06:08, Raymond Wooninck wrote:
upscope wrote:
Did I use the wrong extra repo on my upgrade. I used:
Code: ----------
http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_openSUSE_13...
If you are running an openSUSE 13.1 system and have the KDE:Current repository enabled, then the above link is the right one to find additional KDE/Qt packages/applications.
Regards
Raymond
Oh sweet jesus! What you are saying is that the KDE:/Extra repository which shows up in YaST has been deprecated and is now replaced by KDE:/Extra/KDE_Current_openSUSE_13.1?
Where did you read that? Raymond said that *if* you use KDE:Current *then* you have to use the KDE:Extra:KDE_Current_openSUSE_13.1 repo. If you do not use KDE:Current, you still use KDE:Extra:openSUSE_13.1 repo. KDE:Extra:KDE_Current_openSUSE_13.1 replaces the repos named like KDE:Extra:Extra_Release_412_openSUSE_13.1.
Which is what I was querying in my earlier post that the *standard* KDE/Extra listed in YaST has disappeared.
"Listed in YaST"? Where? YaST is a tool where many things are listed at different places. In my listings, no repository disappeared.
(Why hasn't there been an amendment to YaST to reflect this change?)
Pardon? First read, then act. In this case, read the upgrade instructions before upgrading. You cannot solve an organisatory problem by programming. Werner -- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sunday, April 27, 2014 04:38:27 PM Werner Flamme wrote:
[27.04.2014 09:46] [Basil Chupin]:
On 27/04/14 06:08, Raymond Wooninck wrote:
upscope wrote:
Did I use the wrong extra repo on my upgrade. I used:
Code: ----------
http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_op enSUSE_13.1/
If you are running an openSUSE 13.1 system and have the KDE:Current repository enabled, then the above link is the right one to find additional KDE/Qt packages/applications.
Regards
Raymond
Oh sweet jesus! What you are saying is that the KDE:/Extra repository which shows up in YaST has been deprecated and is now replaced by KDE:/Extra/KDE_Current_openSUSE_13.1?
Where did you read that? Raymond said that *if* you use KDE:Current *then* you have to use the KDE:Extra:KDE_Current_openSUSE_13.1 repo. If you do not use KDE:Current, you still use KDE:Extra:openSUSE_13.1 repo.
KDE:Extra:KDE_Current_openSUSE_13.1 replaces the repos named like KDE:Extra:Extra_Release_412_openSUSE_13.1.
Which is what I was querying in my earlier post that the *standard* KDE/Extra listed in YaST has disappeared.
"Listed in YaST"? Where? YaST is a tool where many things are listed at different places. In my listings, no repository disappeared.
(Why hasn't there been an amendment to YaST to reflect this change?)
Pardon? First read, then act. In this case, read the upgrade instructions before upgrading. You cannot solve an organisatory problem by programming.
Werner Yoy beat me to responding. I got the information from a thread Raymond started (installation instructions) and from the Wiki page I read. -- openSUSE 13.1(Linux 3.11.10-7-desktop x86_64| Intel(R) Quad Core(TM) i5-4440 CPU @ 3.10GHz|8GB DDR3| GeForce 8400GS (NVIDIA-Linux-x86_64-331.49)|KDE 4.12.4
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
upscope wrote:
Did I use the wrong extra repo on my upgrade. I used:
Code: ----------
http://download.opensuse.org/repositories/KDE:/Extra/KDE_Current_openS USE_13.1/
If you are running an openSUSE 13.1 system and have the KDE:Current repository enabled, then the above link is the right one to find additional KDE/Qt packages/applications. Yes I'm om 13.1 and have been using the KDE Current repos, as soon as
On Saturday, April 26, 2014 10:08:36 PM Raymond Wooninck wrote: they were opened (No problems, so far with upgtade).
Regards
Raymond
-- openSUSE 13.1(Linux 3.11.10-7-desktop x86_64| Intel(R) Quad Core(TM) i5-4440 CPU @ 3.10GHz|8GB DDR3| GeForce 8400GS (NVIDIA-Linux-x86_64-331.49)|KDE 4.12.4 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 26/04/14 17:34, Raymond Wooninck wrote:
Basil Chupin wrote:
HOLD IT!
Weren't we told that this KDE/Extra repo is now deprecated and everything is in KDE:/Current?
Or did I get the story wrong?
I guess that you are the one that making things up as you go along. It was never indicated that KDE:Extra would be deprecated. If you took the time to check the KDE Repository wiki on http://en.opensuse.org/SDB:KDE_repositories then you would have seen that KDE:Extra is still there.
I am not trying to recreate a KDE-Tumbleweed here. KDE:Current replaces all the previous KDE:Release:XY repo's and therefore offers the complete KDE SC packages. All the other packages, add-ons, etc are still delivered through the normal repository KDE:Extra.
Raymond
OK, thanks. As I stated I was wondering if I had the story wrong. BC -- Using openSUSE 13.1, KDE 4.13.0 & kernel 3.14.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (16)
-
Anton Aylward -
auxsvr＠gmail.com -
Basil Chupin -
Bob Williams -
CA G Rajesh -
ianseeks -
John Andersen -
Ken Schneider - openSUSE -
Lars Kruczynski -
Pablo Dotro -
Raymond Wooninck -
Ricardo Chung -
Rodney Baker -
upscope -
Werner Flamme -
šumski