[opensuse-project] upgrade oS 13.1
Good morning, not sure if this is the right group to ask, but is there a plan to upgrade the current openSUSE 13.1 to KDE 4.13.3 (or later)? I'm asking for the Official openSUSE build, not the respective KDE Project in Buildservice. Thanks Axel
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 25/06/14 09:17, Axel Braun escribió:
Good morning,
not sure if this is the right group to ask, but is there a plan to upgrade the current openSUSE 13.1 to KDE 4.13.3 (or later)? I'm asking for the Official openSUSE build, not the respective KDE Project in Buildservice.
Thanks Axel
Hi Why don't you add the KDE:current repo to be update? - -- GPG Key: 0xF782C8C2 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTqpRUAAoJEGgEvAX3gsjC4csIAMdxp3u2xvA+FAVsBPtqmxms DoaK5pnFeeRGOFpaVIVad+ma71XhRpP0DZ7x6n7/ci0Fb708KCO2JwFi7XbaDZCH E3wFhLrUdq78qkyQI/ILjplaDqekYAwIvI21xvSS2JS1VZ4kO/1gudwuLwYQ0uhZ rmzt8g58KCApZUaKPxoB9/BGMMa3hk8H6K63EUm6DucvFBKqbzPEe382k9BICsSE QWxR3ur+5nHhlTpPpf+/OfqJEspC6KKuOtj7PlkGUpkmhb6hMX1Ok0Oycd01i/Yp YjYRjuYVJRtLnMrvjJYlRAbsVls0DKqaPd07kUazJ7CFpTjfbxvJA2Pr2lEcUwg= =REeV -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
2014-06-25 6:20 GMT-03:00 victorhck
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
El 25/06/14 09:17, Axel Braun escribió:
Good morning,
not sure if this is the right group to ask, but is there a plan to upgrade the current openSUSE 13.1 to KDE 4.13.3 (or later)? I'm asking for the Official openSUSE build, not the respective KDE Project in Buildservice.
Thanks Axel
Hi Why don't you add the KDE:current repo to be update?
- --
Hi, There are no such plan. The plan for KDE releases on openSUSE is to just update the minor releases of KDE. 13.1 was released with 4.11.1 and was updated until 4.11.5 For newer release use the KDE:Current or Tumbleweed repositories. Regards, Luiz -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-06-25 11:20, victorhck wrote:
Hi Why don't you add the KDE:current repo to be update?
Warning: When 13.1 goes onto Evergreen, people using it might need to revert to the standard 13.1, because the "KDE:current" repo will probably disappear for 13.1. At least, it happened for 11.4 Evergreen. And same for xfce, gnome, etc. extra repos. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOq1VkACgkQtTMYHG2NR9VB6ACeMdVT68H7kCuspAxk6MdJFrET NncAnjXJvBGBRiq+Sho9s/KiB6ZN9APD =xx0f -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
On June 25, 2014 9:57:45 AM EDT, "Carlos E. R."
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2014-06-25 11:20, victorhck wrote:
Hi Why don't you add the KDE:current repo to be update?
Warning: When 13.1 goes onto Evergreen, people using it might need to revert to the standard 13.1, because the "KDE:current" repo will probably disappear for 13.1. At least, it happened for 11.4 Evergreen.
And same for xfce, gnome, etc. extra repos.
Would people use Evergreen and newer DEs? If so, I bet you can convince the devs to keep a 13.1 build going until the end of Evergreen. (3 years, right?) Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-06-28 05:55, Greg Freemyer wrote:
On June 25, 2014 9:57:45 AM EDT, "Carlos E. R." <> wrote:
Hi Why don't you add the KDE:current repo to be update?
Warning: When 13.1 goes onto Evergreen, people using it might need to revert to the standard 13.1, because the "KDE:current" repo will probably disappear for 13.1. At least, it happened for 11.4 Evergreen.
And same for xfce, gnome, etc. extra repos.
Would people use Evergreen and newer DEs? If so, I bet you can convince the devs to keep a 13.1 build going until the end of Evergreen. (3 years, right?)
Dunno. We did not convince them with 11.4 to even "not delete" the repos, leave them frozen. Keep the build? No way. Notice that it is not about using the newest DEs available during the extended maintenance period Evergreen provides. It is about keeping the same advanced version that was used during the normal maintenance period of the distro. Suppose there is a bug somewhere in 11.4 that blocks you (there was, past tense, of course). It is not upgraded on the standard repo, but it is in one of the advanced kde, gnome, xfce repos, whatever. So you use it. After a year, 11.4 goes evergreen... and that repo is deleted. So those packages go red in YaST. If you need to reinstall, or install another machine, add an extra component... you can not. It is just a word of caution. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlOuQQoACgkQtTMYHG2NR9W1cQCfRzsMRZtaX032+HEaYM0yrTrc 5/0AnjvhGi7vYkIACmGn8bqF9z8pCY56 =+qWw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Personally, I agree there are a few "hard bugs" in KDE sc 4.11 that do make remaining there for some a hard choice. Like I gather so many others, I had migrated to KDE:current initially for this reason. However, I also understand the reasoning behind keeping 13.1 on a stable and original baseline release for long term evergreen support. I certainly would like to see KDE:current with at least 4.13 continue for 13.1 for evergreen though... On Saturday, June 28, 2014 06:14:02 AM Carlos E. R. wrote:
On 2014-06-28 05:55, Greg Freemyer wrote:
On June 25, 2014 9:57:45 AM EDT, "Carlos E. R." <> wrote:
Hi Why don't you add the KDE:current repo to be update?
Warning: When 13.1 goes onto Evergreen, people using it might need to revert to the standard 13.1, because the "KDE:current" repo will probably disappear for 13.1. At least, it happened for 11.4 Evergreen.
And same for xfce, gnome, etc. extra repos.
Would people use Evergreen and newer DEs? If so, I bet you can convince the devs to keep a 13.1 build going until the end of Evergreen. (3 years, right?)
Dunno.
We did not convince them with 11.4 to even "not delete" the repos, leave them frozen. Keep the build? No way.
Notice that it is not about using the newest DEs available during the extended maintenance period Evergreen provides. It is about keeping the same advanced version that was used during the normal maintenance period of the distro.
Suppose there is a bug somewhere in 11.4 that blocks you (there was, past tense, of course). It is not upgraded on the standard repo, but it is in one of the advanced kde, gnome, xfce repos, whatever. So you use it. After a year, 11.4 goes evergreen... and that repo is deleted. So those packages go red in YaST.
If you need to reinstall, or install another machine, add an extra component... you can not.
It is just a word of caution.
-- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Am Sonntag, 29. Juni 2014, 17:06:45 schrieb David Sugar:
Personally, I agree there are a few "hard bugs" in KDE sc 4.11 that do make remaining there for some a hard choice. Like I gather so many others, I had migrated to KDE:current initially for this reason. However, I also understand the reasoning behind keeping 13.1 on a stable and original baseline release for long term evergreen support. I certainly would like to see KDE:current with at least 4.13 continue for 13.1 for evergreen though...
and - there is an option to build against e.g. repository=DISCONTINUED_openSUSE_11.3_Update_standard would that be an option for KDE:current? Cheers/Axel
On Saturday, June 28, 2014 06:14:02 AM Carlos E. R. wrote:
On 2014-06-28 05:55, Greg Freemyer wrote:
On June 25, 2014 9:57:45 AM EDT, "Carlos E. R." <> wrote:
Hi Why don't you add the KDE:current repo to be update?
Warning: When 13.1 goes onto Evergreen, people using it might need to revert to the standard 13.1, because the "KDE:current" repo will probably disappear for 13.1. At least, it happened for 11.4 Evergreen.
And same for xfce, gnome, etc. extra repos.
Would people use Evergreen and newer DEs? If so, I bet you can convince the devs to keep a 13.1 build going until the end of Evergreen. (3 years, right?)
Dunno.
We did not convince them with 11.4 to even "not delete" the repos, leave them frozen. Keep the build? No way.
Notice that it is not about using the newest DEs available during the extended maintenance period Evergreen provides. It is about keeping the same advanced version that was used during the normal maintenance period of the distro.
Suppose there is a bug somewhere in 11.4 that blocks you (there was, past tense, of course). It is not upgraded on the standard repo, but it is in one of the advanced kde, gnome, xfce repos, whatever. So you use it. After a year, 11.4 goes evergreen... and that repo is deleted. So those packages go red in YaST.
If you need to reinstall, or install another machine, add an extra component... you can not.
It is just a word of caution.
-- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On Wednesday 25 June 2014 09:17:33 Axel Braun wrote:
Good morning,
not sure if this is the right group to ask, but is there a plan to upgrade the current openSUSE 13.1 to KDE 4.13.3 (or later)? I'm asking for the Official openSUSE build, not the respective KDE Project in Buildservice.
Thanks Axel
Hi Axel, I guess the answer to your question was already given, but some additional background: Official openSUSE distro releases (e.g. 12.3, 13.1) will only receive bugfixes and not new functionality. I know that this is not valid for some leaf packages (e.g. Internet browsers), but definitely the case for KDE, GNOME, etc. Based on these guidelines we have been updating KDE only till the latest minor release for the KDE release that the distro release was shipped with. For oS 13.1, this was KDE 4.11, which we updated to the latest release KDE 4.11.5 through the maintenance channel. A major release of KDE (or any other package) could bring new bugs or even alter requirements and dependencies. So it is not possible to provide these type of updates through the maintenance channel. Therefore the openSUSE KDE Community team is providing these type of updates through a separate KDE repository (KDE:Current) on the Buildservice, which is build for the latest openSUSE distro releases (at this moment for 12.3 and 13.1). If a newer version of a dependency is required, then this update will also be provided through the same repository. The repositories under the KDE Project are maintained by the openSUSE KDE Community team and this team is also providing the necessary KDE packages for the openSUSE distro. So I am not sure what you mean with Official openSUSE build ? If you mean to respin oS 13.1, but then with KDE 4.13.3, then this will not happen. You either have to wait until a newer oS release or utilize the buildservice to get the updates you want. Regards Raymond openSUSE KDE community Team -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org
Hallo Raymond Am Mittwoch, 25. Juni 2014, 15:07:18 schrieb Raymond Wooninck:
The repositories under the KDE Project are maintained by the openSUSE KDE Community team and this team is also providing the necessary KDE packages for the openSUSE distro. So I am not sure what you mean with Official openSUSE build ? If you mean to respin oS 13.1, but then with KDE 4.13.3, then this will not happen.
Yes, that was exactly the question. It would be a nice situation to have the system maintained long term, but at the same time getting fixes for KDE. Carlos has pointed out what the situation within Evergreen will be. And some annoying bugs like https://bugs.kde.org/show_bug.cgi?id=331156 make life on the current 4.11.5 KDE really hard.... Best regards Axel
participants (7)
-
Axel Braun -
Carlos E. R. -
David Sugar -
Greg Freemyer -
Luiz Fernando Ranghetti -
Raymond Wooninck -
victorhck