Re: How to handle upgrades to Fedora 21

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/24/2014 06:22 PM, Jaroslav Reznik wrote:
----- Original Message -----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There has been some discussion in various forums lately about how we
will handle fedup upgrades from Fedora 20 to Fedora 21 products.

Several suggestions have been made that warrant discussion:

  * Upgrades from Fedora 20 remain non-productized. They pick up
fedora-release-standard and upgrade only their existing packages.
  * Upgrades from Fedora 20 become Fedora Workstation systems and have
the appropriate environment group installed on them. This mechanism
will not remove any existing packages.
  * Fedup should provide a selection for which Product (or
non-productized) version to upgrade to.

I am personally opposed to forcing all upgrades to become Fedora
Workstation (even if in general the majority of existing deployments
are desktop/laptop machines).

I think either the first option (easy) or the last option (requiring
fedup changes) will be preferable. In the selectable case, I think
that fedup should operate as a non-productized upgrade unless
otherwise specified at the command-line. If we pass --server,
- --workstation, --cloud, it should upgrade existing packages as well as
installing the complete set of the @^fedora-$PRODUCT-environment comps
environment group.
Maybe we can go with first option and say, upgrades to products are not
supported, please reinstall. It's new beginning and say non-productized
update support will be gone in F22 timeframe and only productized updates
will be allowed.
In RHEL we are using preupgrade-assistant [1] which does this work.
If user write a check script then it will inform user that upgrade is not supported.
The check script can also inform user that e.g. mariadb changed structure
and it's required to execute a convert script or whatever.

Currently now preupgrade-assistant is not available in Fedora.
I discussed with Honza Horak (team lead of databases) about this issues
and can be used in this case.

There is only one issue. Each package maintainer should create own subpackage with check script
which should be used on Fedora.
And I think that this is a bit problematic. From time point of view

[1] https://github.com/phracek/preupgrade-assistant

In Czech we say "Když se kácí strom, létají třísky" - Google Translate
is your friend :).

Jaroslav

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlQi7kYACgkQeiVVYja6o6OMSACgjZqFxjISnfEhVVSXWLs7HENf
cIwAoK6e/Dp1uLvVX1feUr4gouTwhKsd
=U4A7
-----END PGP SIGNATURE-----
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct


--
Best regards / S pozdravem
Petr Hracek

--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux