Description of problem: hi, i've noticed that using mageiaupdate it doesn't prompt any updates for my mageia 1, while if i use urpmi --auto-update comand i have no problems... Tell me if you need more info cheers, Marcello
MageiaUpdate only considers "updates" sources, whereas urpmi --auto-update considers all "enabled" sources. There are no updates for Mageia 1 ATM, so it's expected that MageiaUpdate will show nothing.
Status: NEW => RESOLVEDResolution: (none) => INVALID
how come they are uploaded in the /release tree even if they are updates??
Do you have the tainted repo enabled? If so then packages from /tainted/release will be reported (by urpmi and rpmdrake, but not Mageia Update) as updates to the equivalent packages in /core/release. This is so that people who want to use those packages instead of the core packages can do so. This is similar to what happened on Mandriva, where plf packages were reported as updates to the equivalent official packages.
*** Bug 1840 has been marked as a duplicate of this bug. ***
CC: (none) => eagle150
"MageiaUpdate only considers "updates" sources, whereas urpmi --auto-update considers all "enabled" sources." Well, why is that? Obviously that is a bug. Why was this (and the other bugreport) marked as invalid? It is not invalid at all! Urpmi --auto-update is supposed to...well, automatically update packages, just as the MCC function should. So please explain to me why you don't consider that a bug?
Testing and Backports sources are not marked as update repos by default. Check /etc/urpmi/urpmi.cfg Repos that have update line in their conf are checked by MCC. So you can add it manually and it will work. But by default those are not marked as update repos as they can harm system if used wrongly :)
CC: (none) => sander.lepik
Yes, I get that, but still, backports and testing-repos are not installed by default, are they? If they are not installed by default, that means that the user has to activate them manually. So I don't really see why the MCC should show different results than the Console, since there is no real danger for newbies to destroy their system anyways. Advanced users may want to check what updates are in backports or testing via MCC for different reasons and IMHO they shouldn't have to mess around with the config-file to do so... well, that is my opinion, anyways, thanks for giving yours.
When you add default repos they will be all listed. Unchecked but still listed. I already saw a forum post where one novice user suggested to select a lot of those mirrors. I'm not sure how many fallowed but if those repos would have update ability. I don't wanna think about that. If you are advanced user you can enable those and have no problem. If you are novice user following some dumb advice you may crash your system really bad.
(In reply to comment #5) > "MageiaUpdate only considers "updates" sources, whereas urpmi --auto-update > considers all "enabled" sources." > > Well, why is that? Obviously that is a bug. Why was this (and the other > bugreport) marked as invalid? It is not invalid at all! > > Urpmi --auto-update is supposed to...well, automatically update packages, just > as the MCC function should. So please explain to me why you don't consider that > a bug? It's no a bug because */release repos are _never_ changed after the official release of a distro (Mageia 1 in this case), updated packages go to */updates.
(In reply to comment #7) > Yes, I get that, but still, backports and testing-repos are not installed by > default, are they? If they are not installed by default, that means that the > user has to activate them manually. So I don't really see why the MCC should > show different results than the Console, since there is no real danger for > newbies to destroy their system anyways. Advanced users may want to check what > updates are in backports or testing via MCC for different reasons and IMHO they > shouldn't have to mess around with the config-file to do so... > > well, that is my opinion, anyways, thanks for giving yours. Users don't necessarily need to edit any config files if they want to, you can use drakrpm-edit-media configure the repos any way you want (in some cases you have to use 'drakrpm-edit-media --expert').
I forgot to say that rpmdrake has a Backports filter, which shows packages from backports repos even if they're disabled, it's done this way to make it easier for users to install packages from Backports.
"It's no a bug because */release repos are _never_ changed after the official release of a distro (Mageia 1 in this case), updated packages go to */updates." Yes, I know that, but I fail to see how that is relevant. The same packages are in backports, so I asumed MCC and Console should show the same results, but Sander Lepik explained why that isn't the case. But what Ahmad Samir is saying kind of contradicts that: Do you want to protect users from "destroying" their system with the backports or do you want to make it easy to install packages from backports? I don't think you can do both, so which one is it? I think you maybe should have a discussion about that if you haven't already.
Users can search for backported packages and install them one by one. But they won't get installed as updates so it would replace bunch of packages w/o user knowing. That is not good practice..
Source RPM: mageiaupdate => mgaonline
*** Bug 1853 has been marked as a duplicate of this bug. ***
CC: (none) => isis2000