One of the reasons why users wince at the prospect of upgrading is the
numerous problems being encountered.
Some of these problems seem to stem from the fact that not all installed
rpms of the current release (let's say 21) are made available in f22.
Now the user mosies on thinking all is well. Until some updates come
up later which will prevent those updates from being installed,because
of the dependencies of packages installed in the previous release upon
packages which are still of the previous release vintage. As you all know,
the dependencies do not satisfy the requirements of only one package, but
possibly of several other packages. Thus the update of certain dependencies
will fail because a remnant or remnants from the previous release has/have
no presence in the new release's repo.
So, I am wondering if the thought has even crossed the minds of the fedora
project architects/managers/directors to properly address this issue.
I have been a victim f this particular issue ever since the early fedora
core
days.
I suggest that the fedora project consider either
1. the creation or porting of the previous release packages and their
dependencies into the new release
OR
2. the deprecation of packages that will not see the light of day in the
new release, and creation of replacements for them.
That said, I am totally against the elimination of those packages from the
user's system just to please the update and upgrade processes. Somehow
fedora project needs to come up with a scheme to let the previous
release's packages
and their dependencies to continue to live and work in the new release and
subsequent releases without raising any problems or errors for updates and
upgrades.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
