Re: [gentoo-user] kde 3.5 packages blocking each other
On Monday 15 June 2009 03:32:57 Francisco Ares wrote: I've found out that there are some packages out of kde-basse that are pulling 3.5.10 packages while they're still masked ~x86 One is Amarok. Another, probably, is Ktorrent. Amarok-1.4 will pull in kdelibs-3.5.10 Amarok-2.1 will pull in kdelibe-4 ktorrent also has a 3.5 and a 4 port. k3b is still kde-3 only -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] kde 3.5 packages blocking each other
Thanks again - going into kde-meta, it seems that everything will be ok Francisco On Mon, Jun 15, 2009 at 3:57 AM, Alan McKinnonalan.mckin...@gmail.com wrote: On Monday 15 June 2009 03:32:57 Francisco Ares wrote: I've found out that there are some packages out of kde-basse that are pulling 3.5.10 packages while they're still masked ~x86 One is Amarok. Another, probably, is Ktorrent. Amarok-1.4 will pull in kdelibs-3.5.10 Amarok-2.1 will pull in kdelibe-4 ktorrent also has a 3.5 and a 4 port. k3b is still kde-3 only -- alan dot mckinnon at gmail dot com -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have one idea and we exchange these ideas, then each of us will have two ideas. - George Bernard Shaw
Re: [gentoo-user] kde 3.5 packages blocking each other
I've found out that there are some packages out of kde-basse that are pulling 3.5.10 packages while they're still masked ~x86 One is Amarok. Another, probably, is Ktorrent. Anyone has seen it or am I the only one not using KDE 4 ;-) ? Best regards to all Francisco On Sat, Jun 13, 2009 at 5:58 AM, Alan McKinnon alan.mckin...@gmail.comwrote: On Saturday 13 June 2009 01:54:45 Francisco Ares wrote: Thanks a lot! It's not completely obvious from Dirk's post (what he said is completely accurate though), but kde-3.5.10 will not receive monolithic ebuilds (dev decision). If you want kde-3.5.10, there is only one way to do it - Unmerge your existing kde monolithic packages Rememerge the new kde split packages There's a good migration guide at gentoo.org, called Migrating to KDE split ebuilds or some such. A quick search will find it for you. Francisco On Fri, Jun 12, 2009 at 5:58 PM, Dirk Heinrichs dirk.heinri...@online.dewrote: Am Freitag 12 Juni 2009 22:45:49 schrieb Francisco Ares: And how do I tell if an ebuild is monolithic or not? The monolithic ones install larger parts of KDE, and usually have the same names as the original source packages offered at KDE.org. The split ebuilds, well, split those packages into their individual applications, so you have ebuilds for konqueror (which is also part of kdenetwork) or kmail (kdepim). In addition, there are the -meta ebuilds, which have the same name as the monolitic ones, but with -meta appended (kdepim-meta). Those usually install the same applications than monolithic ebuilds, but as split ebuilds. So, when you install kde, you get a complete KDE from monolithic ebuilds and when you install kde-meta, you get a complete KDE from split ebuilds. That's also the reason why they block each other. When you have kdepim installed, you already got kmail, so you shouldn't install kmail from the split ebuild again. HTH... Dirk -- alan dot mckinnon at gmail dot com -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have one idea and we exchange these ideas, then each of us will have two ideas. - George Bernard Shaw
Re: [gentoo-user] kde 3.5 packages blocking each other
On Saturday 13 June 2009 01:54:45 Francisco Ares wrote: Thanks a lot! It's not completely obvious from Dirk's post (what he said is completely accurate though), but kde-3.5.10 will not receive monolithic ebuilds (dev decision). If you want kde-3.5.10, there is only one way to do it - Unmerge your existing kde monolithic packages Rememerge the new kde split packages There's a good migration guide at gentoo.org, called Migrating to KDE split ebuilds or some such. A quick search will find it for you. Francisco On Fri, Jun 12, 2009 at 5:58 PM, Dirk Heinrichs dirk.heinri...@online.dewrote: Am Freitag 12 Juni 2009 22:45:49 schrieb Francisco Ares: And how do I tell if an ebuild is monolithic or not? The monolithic ones install larger parts of KDE, and usually have the same names as the original source packages offered at KDE.org. The split ebuilds, well, split those packages into their individual applications, so you have ebuilds for konqueror (which is also part of kdenetwork) or kmail (kdepim). In addition, there are the -meta ebuilds, which have the same name as the monolitic ones, but with -meta appended (kdepim-meta). Those usually install the same applications than monolithic ebuilds, but as split ebuilds. So, when you install kde, you get a complete KDE from monolithic ebuilds and when you install kde-meta, you get a complete KDE from split ebuilds. That's also the reason why they block each other. When you have kdepim installed, you already got kmail, so you shouldn't install kmail from the split ebuild again. HTH... Dirk -- alan dot mckinnon at gmail dot com
[gentoo-user] kde 3.5 packages blocking each other
Hi As I'm still on KDE 3.X, I've got several package updates, but most of them are blocking each other: [blocks B ] kde-base/kcontrol:3.5 (kde-base/kcontrol:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kicker:3.5 (kde-base/kicker:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/libkonq:3.5 (kde-base/libkonq:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kdeedu (kde-base/kdeedu is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/konqueror:3.5 (kde-base/konqueror:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kdialog:3.5 (kde-base/kdialog:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] =kde-base/kdebase-3.5* (=kde-base/kdebase-3.5* is blocking kde-base/kmenuedit-3.5.10, kde-base/kdialog-3.5.10, kde-base/kdebase-kioslaves-3.5.10-r1, kde-base/kicker-3.5.10-r1, kde-base/kdebase-data-3.5.10, kde-base/kfind-3.5.10, kde-base/kcminit-3.5.10, kde-base/kdesu-3.5.10, kde-base/konqueror-3.5.10, kde-base/khotkeys-3.5.10, kde-base/khelpcenter-3.5.10, kde-base/libkonq-3.5.10, kde-base/kcontrol-3.5.10) [blocks B ] kde-base/kdeaddons (kde-base/kdeaddons is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kdeutils (kde-base/kdeutils is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kcminit:3.5 (kde-base/kcminit:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kde (kde-base/kde is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kdetoys (kde-base/kdetoys is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kdebase-kioslaves:3.5 (kde-base/kdebase-kioslaves:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kfind:3.5 (kde-base/kfind:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kdepim (kde-base/kdepim is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kdebase (kde-base/kdebase is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kmenuedit:3.5 (kde-base/kmenuedit:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kdegraphics (kde-base/kdegraphics is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kdewebdev (kde-base/kdewebdev is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kdegames (kde-base/kdegames is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/khotkeys:3.5 (kde-base/khotkeys:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kdenetwork (kde-base/kdenetwork is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kdebase-data:3.5 (kde-base/kdebase-data:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kdemultimedia (kde-base/kdemultimedia is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kdeadmin (kde-base/kdeadmin is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/kdesu:3.5 (kde-base/kdesu:3.5 is blocking kde-base/kdebase-3.5.9-r4) [blocks B ] kde-base/kdeartwork (kde-base/kdeartwork is blocking kde-base/kdelibs-3.5.10-r6) [blocks B ] kde-base/khelpcenter:3.5 (kde-base/khelpcenter:3.5 is blocking kde-base/kdebase-3.5.9-r4) It looks like there's some issue in some packages being 3.5.10 and all the rest being 3.5.9, but I have no keywords set in /etc/portage/packages.keywords - perhaps I should. Any hints? Thanks a lot Francisco -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have one idea and we exchange these ideas, then each of us will have two ideas. - George Bernard Shaw
Re: [gentoo-user] kde 3.5 packages blocking each other
Am Freitag 12 Juni 2009 22:24:26 schrieb Francisco Ares: It looks like there's some issue in some packages being 3.5.10 and all the rest being 3.5.9, but I have no keywords set in /etc/portage/packages.keywords - perhaps I should. Partly. It seems to be a mix of split ebuilds and monolithic ones. You should decide which one to use. The other part is indeed a version mix, because the monolithic ebuilds are still at 3.5.9. HTH... Dirk signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] kde 3.5 packages blocking each other
Am Freitag 12 Juni 2009 22:45:49 schrieb Francisco Ares: And how do I tell if an ebuild is monolithic or not? The monolithic ones install larger parts of KDE, and usually have the same names as the original source packages offered at KDE.org. The split ebuilds, well, split those packages into their individual applications, so you have ebuilds for konqueror (which is also part of kdenetwork) or kmail (kdepim). In addition, there are the -meta ebuilds, which have the same name as the monolitic ones, but with -meta appended (kdepim-meta). Those usually install the same applications than monolithic ebuilds, but as split ebuilds. So, when you install kde, you get a complete KDE from monolithic ebuilds and when you install kde-meta, you get a complete KDE from split ebuilds. That's also the reason why they block each other. When you have kdepim installed, you already got kmail, so you shouldn't install kmail from the split ebuild again. HTH... Dirk signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] kde 3.5 packages blocking each other
Thanks a lot! Francisco On Fri, Jun 12, 2009 at 5:58 PM, Dirk Heinrichs dirk.heinri...@online.dewrote: Am Freitag 12 Juni 2009 22:45:49 schrieb Francisco Ares: And how do I tell if an ebuild is monolithic or not? The monolithic ones install larger parts of KDE, and usually have the same names as the original source packages offered at KDE.org. The split ebuilds, well, split those packages into their individual applications, so you have ebuilds for konqueror (which is also part of kdenetwork) or kmail (kdepim). In addition, there are the -meta ebuilds, which have the same name as the monolitic ones, but with -meta appended (kdepim-meta). Those usually install the same applications than monolithic ebuilds, but as split ebuilds. So, when you install kde, you get a complete KDE from monolithic ebuilds and when you install kde-meta, you get a complete KDE from split ebuilds. That's also the reason why they block each other. When you have kdepim installed, you already got kmail, so you shouldn't install kmail from the split ebuild again. HTH... Dirk -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have one idea and we exchange these ideas, then each of us will have two ideas. - George Bernard Shaw
