When magic becomes tragic - upgrading from 1 to 2 [Solved]

[msdobrescu]

Code: Select all

rpm -qa | grep mga1

will give you the list, so you could try something like

Code: Select all

urpme $(rpm -qa | grep mga1)

but i think that would only do damage, and not help at all.

But, i'll ask again, is there some particular problem with one of the mga1 packages?

I have used

Code: Select all

rpm -qa | grep mga1

to get the installed mga1 packages, I have got the list from a mirror and compared them, now I am cleaning.

Please warn people about this

Code: Select all

urpme $(rpm -qa | grep mga1)

. This will remove all the mga1 packages, even the ones being part of Mageia 2 version and all their dependents. It is a kind of 'do it yourself virus'.

Thinking on errata, well, some might still try, hoping it won't happen any crash (trusting Mageia team). When it crashes, they become experienced users (if they are not already) . I do not complain about the crash, but about not including the non-free drivers for the video cards in the DVD/CDs. Here I completely ignore the legal issues with that.
I have bought a TV Tunner that included a chip - many brands had it at that time - and the support team of the producer recommended the tuner as being supported on linux. I've got it and it didn't work because the chip producer did not allow making open source drivers (not necessarily free). Now, the chip maker doesn't exist anymore. And the great team of v4l made drivers and I can watch TV on linux. I know that nVidia or Ati are much less likely to disappear as that chip producer, but still, why would they request fees or forbid distribution of their drivers? This is a major pain for the users.It's like you buy a car and purchase the keys separately because you wear blue instead of red shirt...

[doktor5000]

Please only one problem per thread, don't mangle them all together.

About comparing the packages, why do you want to do something which urpmi does by itself? urpmi --auto-update compares the packages available in the current available repositories against the installed ones, whether the repos are marked as update media or not (which the update applet does not, it only installs updates from update media. FWIW you can enable/disable update status of repos via drakrpm-edit-media --expert)
For the other direction, to list all packages which are not available from any repository, use urpmq --not-available

[doktor5000]

Please warn people about this

Code: Select all

urpme $(rpm -qa | grep mga1)

. This will remove all the mga1 packages, even the ones being part of Mageia 2 version and all their dependents. It is a kind of 'do it yourself virus'.

Well, you asked for a way how to do this, and i showed you one, even if i told you that's useless as there are still many mga1 packages in Mageia 2 which are needed.
You seem to by quite confused. First you ask for something, and now you tell that we should warn users about that something which you explicitly asked for, after being told that's not good and could be quite detrimental ...
You should maybe make up your mind.

[msdobrescu]

Thanks, urpmq --not-available is what I need.

My OS is Mandriva updated to Mageia 1 and then to Mageia 2.
What public keys should I have if I freshly install Mageia 2?

[isadora]

Msdobrescu, please use dedicated topics for each and every subject!!!!

[msdobrescu]

Msdobrescu, please use dedicated topics for each and every subject!!!!

Please excuse me, but this refers to the upgrading process entirely, solving the conflicts and cleaning up the system after the upgrade.
The keys are related to that and might be a cause of the problem - IMHO.
That's why I have posted everything here.
Otherwise, I would have had to describe again and again how I've got to ask this and that.
So, IMHO, they are all related.
If you think they are different, please explain, so I won't make this mistake again

Thank you.

[isadora]

Understood, and accepted.

[ihowarth]

My on-line upgrade from Mandriva 2010.2 to Mageia 1 was the smoothest i've ever experienced (since...1995?) - completely flawless, i didn't have to tweak ANYTHING afterwards. Mega impressed. Because i have several machines, i decided to upgrade to Mageia 2 from DVD (to save repeated big downloads)...what a disaster! The first "upgrade" left me with an unbootable system. Rebooting from DVD, a repeat upgrade got me to a locked splash screen (and i've always disabled splash screens - i want to see what's going on), but i was able to ssh in, and urpmi --auto-select to get to something bootable from HDD. Still plenty of broken bits and pieces that i'm slowly working through - i'll probably just wipe and do a clean install.

This is obviously related to bug 5687, but, come on, shouldn't an issue that leaves hundreds of uninstalled packages have been picked up sooner?

[isadora]

...................................... but, come on, shouldn't an issue that leaves hundreds of uninstalled packages have been picked up sooner?

You are right, and that is the very reason we keep on asking people to contribute.
The more contributors the more can be handled.

So feel free, but take a short while for:
https://www.mageia.org/en/contribute/

[msdobrescu]

Yeah! Shame on you!... Or not.
I've got several situations. But even samba removed during upgrade, the configs were kept, so I could just install the right packages and everything works as before.
This shows the quality of the distro itself.
The paradox: the crash reveals the power instead of weakness - the logic of upgrade is in the users favor.

Thanks for the good work!

[ihowarth]

Yep, i own up to being unfairly grumpy, and agree that it's a great, fundamentally solid distro. I'd just supposed that something so obviously problematical would've been picked up sooner, but you're right, as a community supported distro it's as much my responsibility as anyone's to at least contribute bug alerts, even if i'm not competent to fix them. Mea culpa!

[isadora]

[msdobrescu]

Hello,

What public keys should I have if I freshly install Mageia 2?
They are shown in Software Manager...

[doktor5000]

For a fresh default install of Mageia 2, querying the default gpg-pubkeys via

Code: Select all

rpm -qa | grep gpg-pubkey

you should get gpg-pubkey-80420f66-4d4fe123 as a result. Other gpg-pubkeys may be there from before the upgrade.

But why do you ask? If there are no gpg check issues when installing packages that doesn't really matter and is of less relevance...
What are you trying to do actually?

[msdobrescu]

I have upgraded Mandriva to Mageia, so I have several keys, Mandrake, Mandriva and Mageia.
I would like to erase the old ones, and keep Mageia only, if that's right. I don't know if you keep the old ones for some compatibility, or they are simply left by the upgrades.

Code: Select all

gpg-pubkey-70771ff3-3c8f768f
gpg-pubkey-80420f66-4d4fe123
gpg-pubkey-22458a98-3969e7de
gpg-pubkey-26752624-3fd74faa
gpg-pubkey-78d019f5-3fd7504d

[doktor5000]

What do you assume, which benefit will that bring? Exactly none. But feel free to remove as much as you want, if that makes you more happy.

[msdobrescu]

Will this forbid installing other distro packages? Or at least, would I have a warning?

[doktor5000]

As root nothing is forbidden. It will spit out a warning about unknown GPG key or something like that, but what's the benefit?
If you don't have any other repos, and as you shouldn't use directly other distro packages normally, what's the advantage? Where's the use case?

[msdobrescu]

I do install sometimes 'alien' software, RawTherapee, for example. And some others that are not available or have much newer versions I would like to try.
That's why I like rolling releases.
Right now, I would like to close this thread as 'solved', as my Mageia works perfectly.