[SOLVED] Update Testing/64 bit/32 bit

[random12]

I want to comment on a defect in a way adding the update testing repositories works.

I've been with Mandrake/Mandriva/Mageia since the end of Mandrake, 10 or 10.1 or whatever that was.

I'm not sure if this is a defect with the control center add/remove software or just the way people are shoving things into update testing.

I've installed Mageia 1 64 bit on a fancy new machine. (My first new desktop in 7 years). I like to keep my internet access secure, so I thought I'd add the update testing repositories so I could add the latest javas, firefoxes, etc. which have many security fixes.

When I go to add/remove software via the control center now, I see a fair number of rpms that look fancy and new and better that the controls center suggests I install by showing a blue download arrow. They're fancy and new and better than their old 32 bit ancestor. I'm running 64 bit and have the 64 bit equivalent of the ancestor. It seems that somebody is focused on adding 32 bit updates but doesn't care about making a 64 bit update available as well.

Luckily when I try actually add one of these update packages I just get a cryptic "Sorry you can't do that message."

It's bullshit though. As ESR would say, if I can't do it, why should I be given the option to do it.

Can we either not let 32 bit packages be seen as replacements for 64 bit packages, or can we make sure that if we're adding something to update testing we do it for both 32 and 64 bit?

Duh?

[doktor5000]

A 32bit package is no replacement for an x86_64 package. Never happened anytime here. Only thing is, when you have a noarch package,
then that is duplicated to both 32bit and x86_64. But it doesn't matter from where this gets installed. Also i'd like to see the output of
urpmq --list-url

Also without the exact error message and such a vague description (this happened with which packages) it's hard to diagnose.
I'm on a x86_64 system here, and i also have updates_testing activated, and no problem with it.

[random12]

Aargh. My bad. Somehow I had missed enabling the core updates testing repository even though
I had enabled all the other updates testing repositories.

The attached BadUpdate screenshot shows what was happening, using firefox as an example.

Once I enabled core updates testing the 64 bit packages are there as you can see from the
OKUpdate screenshot

Sorry for wasting your time.

Regards,
Aaron

[doktor5000]

Well, what does urpmi firefox-5.0.1 (as root in a terminal) tell?
I'm already at Firefox 6.0, so i can't reproduce easily.

[random12]

Well I went ahead and installed the 64 bit firefox 5 after enabling the core updates testing repository, so I'm not sure
that I can help now either.

$ urpmi firefox-5.0.1
bash: urpmi: command not found

Did you mean urpmi.update?
$ urpmi.update firefox-5.0.1
trying to select nonexistent medium "firefox-5.0.1"
the entry to update is missing
(one of Core Release, Core Release Debug, Core Updates, Core Updates Debug, Core Updates Testing, Core Updates Testing Debug, Core Backports, Core Backports Debug, Core Backports Testing, Core Backports Testing Debug, Nonfree Release, Nonfree Release Debug, Nonfree Updates, Nonfree Updates Debug, Nonfree Updates Testing, Nonfree Updates Testing Debug, Nonfree Backports, Nonfree Backports Debug, Nonfree Backports Testing, Nonfree Backports Testing Debug, Tainted Release, Tainted Release Debug, Tainted Updates, Tainted Updates Debug, Tainted Updates Testing, Tainted Updates Testing Debug, Tainted Backports, Tainted Backports Debug, Tainted Backports Testing, Tainted Backports Testing Debug, Core 32bit Release, Core 32bit Release Debug, Core 32bit Updates, Core 32bit Updates Debug, Core 32bit Updates Testing, Core 32bit Updates Testing Debug, Core 32bit Backports, Core 32bit Backports Debug, Core 32bit Backports Testing, Core 32bit Backports Testing Debug)

At any rate, the problem was definitely my user error by not having a repository enabled. We can quibble about whether the control center should have even been showing me things that I couldn't install or whether it could have given a more helpful error message, but I imagine there are higher priority things to focus on.



Regards,
Aaron

[doktor5000]

Well, what does urpmi firefox-5.0.1 (as root in a terminal) tell?

You launched the command as normal user. You need to get root first, with

Code: Select all

su -

And the error message you got was clearly a user error. Because i just tried that, and with updates_testing
disabled you won't get anything from that repository to show. Maybe you had something else wrong.

[random12]

[root@localhost aaron]# urpmi firefox-5.0.1
Package firefox-5.0.1-1.3.mga1.x86_64 is already installed

But that's now after I fixed my mistake.

Again, I'm not sure how it happened, but I had 32 bit updates testing enabled, but not 64 bit updates testing.
With neither I wouldn't see firefox 5. With both I would see two firefox 5's and know that I should install the 64 bit one, not the 32, which is what I did. With just one I had the problem in the screenshot. It was my error.