|Main Archive Page > Month Archives > fedora-users archives|
On 10/10/2011 01:11 PM, suvayu ali wrote:
> On Mon, Oct 10, 2011 at 9:40 PM, JD<email@example.com> wrote:
>> I tried preupgrade.
>> I tried upgrade via DVD.
>> I tried upgrade via yum according to
>> All of them failed to upgrade the system to full F16.
>> Upgrading via all these methods left hundreds of
>> F14 packages in place, even though they were
>> installed via yum update from fedora updates
>> repository, for which F16 updates were indeed
>> identified by yum, but at the same time yum would
>> then say "Not found".
>> I had taken care to disable other repo files, such as
>> rpmfusion, adobe, google, skype, atrpms so as not
>> to get a whole bunch of errors unrelated to upgrading
>> from fedora repos.
> Are you sure they were not packages which were _not_ rebuilt for the
> new release. This is common practice unless there is a significant
> change in any of the packaging utilities (e.g. when RPM changed to a
> sha256 hash).
> To give you an idea, this is what I have on my (never upgraded) F14 system:
> # uname -r
> # rpm -qa | grep -c -E 'fc14|noarch'
> # rpm -qa | grep -c fc13
> # rpm -qa | grep -c fc12
> # rpm -qa | grep -c fc11
> # rpm -qa | grep -c fc10
> And since you pointed to the fedora wiki page, I think I can safely
> assume you did a distro-sync after the upgrade. Despite all the
> precautions an upgrade is a complicated process and often things go
> wrong. Since you have tried all 3 methods and failed, have you
> considered if there is any common point of failure which is hampering
> all the methods?
> Just a few thoughts. Hope this helps.
> PS: My experience with upgrades have been extremely smooth, specially
> when I used preupgrade.
Well, if packages not present in a previous release,
should not the new packages that replace them be
marked as "obsoletes <package name>" ?
Or if they are not even replaced by a new package,
should yum just throw up it's hands and exit with
As I explained my current installation of f14, I also
make use rpmfusion and atrpms repos, which which
I disable during upgrade to avoid complications.
Perhaps that is indeed a source/cause of the failure.
If it is, then clearly it is an issue that should be addressed,
or advise fedora users that making use of other repos
will lead to upgrade failures.
-- users mailing list firstname.lastname@example.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines