Re: [Mageia-dev] ksnapshot conflicts with kdegraphics4-devel
2011/7/5 Radu-Cristian FOTESCU : > fwang, > mikala, > > # urpmi kdegraphics4-devel > The following package has to be removed for others to be upgraded: > ksnapshot-4.6.90-1.mga2.i586 > (due to conflicts with kdegraphics4-devel[<= 2:4.6.90]) (y/N) The conflicts against kdegraphics4-devel was added because somes files were wrongly available in the « old » -devel package & especially the -devel package was not expected to live again . > Or, the other way around: > > # urmpi ksnapshot > The following package has to be removed for others to be upgraded: > kdegraphics4-devel-4.6.90-1.mga2.noarch > (due to conflicts with ksnapshot-4.6.90-1.mga2.i586) (y/N) > > > I admit I don't understand the new KDE 4.7 package "fragmentation" (why must > they always change something upstream? I'm sick of this), but is this normal? > I guess not. > > ksnapshot can coexist with kdegraphics4, but not with kdegraphics4-devel. > In fact kdegraphics4-devel should not exist anymore, i'll remove it from the kdegraphics4 meta package. You should directly install the -devel package you need to build your package from libksane-devel , libkipi-devel, libkexiv2-devel or libkdcraw-devel Fwang > i can understand that you want to keep an empty metapackage (even if i'm personnaly not agree as said earlier) for kdegraphics, but why adding a -devel metapackage here j ? I also noticed you did the same things for kdeedu so i'll remove it too. -- Balcaen John Jabber-id: mik...@jabber.littleboboy.net
Re: [Mageia-dev] ksnapshot conflicts with kdegraphics4-devel
2011/7/6 John Balcaen : > Fwang > i can understand that you want to keep an empty metapackage > (even if i'm personnaly not agree as said earlier) for kdegraphics, > but why adding a -devel metapackage here j ? > I also noticed you did the same things for kdeedu so i'll remove it too. Then please rebuild the relevant packages before doing this. And, obsoletes are not the correct place for solve such problems. > > > > -- > Balcaen John > Jabber-id: mik...@jabber.littleboboy.net >
Re: [Mageia-dev] ksnapshot conflicts with kdegraphics4-devel
On Wednesday 06 July 2011 18:28:27 Funda Wang wrote: > 2011/7/6 John Balcaen : > > Fwang > i can understand that you want to keep an empty metapackage > > (even if i'm personnaly not agree as said earlier) for kdegraphics, > > but why adding a -devel metapackage here j ? > > I also noticed you did the same things for kdeedu so i'll remove it too. > > Then please rebuild the relevant packages before doing this. It was expected but you suddenly start to change things. > And, > obsoletes are not the correct place for solve such problems. ksnapshot don't have any obsoletes but a conflict (which is probably indeed too much but was not expected to add any problem if you were not pushing again the -devel package) Regarding others obsoletes i put them in a specific library (for each project kdegraphics4 & kdeeedu4) because i wanted to drop them from BS too in the same way but you removed them on the same movement when you pushed by the -devel package. -- Balcaen John Jabber ID: mik...@jabber.littleboboy.net
Re: [Mageia-dev] ksnapshot conflicts with kdegraphics4-devel
>> obsoletes are not the correct place for solve such problems. > ksnapshot don't have any obsoletes but a conflict (which is probably > indeed too much but was not expected to add any problem i Sorry to bother you, but since this is both about an upgrade and a change of package names (albeit via a fragmentation/split), why isn't "Obsoletes" a better choice? If I am not very wrong, technically "Conflicts" will cause the install/upgrade to fail and therefore forbids an installation/upgrade. Which is both annoying and it requires a multiple-step action from the end-user's part. In contrast, "Obsoletes" forces an upgrade to the new packages names, automatically removing the old packages. While in principle "Obsoletes" doesn't prevent the end-user from reinstalling the old package(s), this is not desired anyway. I mean, it's not like "kdesomething-4.6.4" and "kdesomesplitpackage-4.6.90" would coexist on the same machine -- it's either you upgraded from KDE 4.6.4 to 4.6.90, or you didn't. So I suppose you say "Obsoletes" is not the right thing to do _as a principle_ (as a principle, GOTO is considered harmful too), but why is it unsuitable for this very case of an evolving (cauldron) repository in a situation of a kinky upgrade? Of course, I am still waiting for a mentor, so I might be very, very wrong in my understanding of "Conflicts vs Obsoletes". What I believe I know is that "Obsoletes" makes things transparent for the end-user, whereas "Conflicts" looks like an error... R-C aka beranger
