[opensuse-factory] Planned release schedule for Leap 42.2
Hi, Time flies, so let's start planning the schedule for Leap 42.2. The current version 42.1 is based on SLE12 SP1 and 42.2 is meant to be based on SP2¹. SLE12 SP2 is expected to reach the beta phase mid of May which means we'll get the package sources in OBS then. That in turn will allow us to start building Leap on top. My plan would be to have a first Alpha end of May based on 42.1 sources with the SLE bits updated to SP2. The next snapshot should be before OSC in June and another one in July. I'd aim for the the first Beta last week of August, followed by Beta2 around September 21st. RC1 would then be Oct 6, followed by RC2 Oct 18. GM Oct 27 so we can release November 2nd. cu Ludwig [1] https://en.opensuse.org/Portal:42.1 -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Mon, 21 Mar 2016 11:14, Ludwig Nussel wrote:
Hi,
Time flies, so let's start planning the schedule for Leap 42.2. The current version 42.1 is based on SLE12 SP1 and 42.2 is meant to be based on SP2¹. SLE12 SP2 is expected to reach the beta phase mid of May which means we'll get the package sources in OBS then. That in turn will allow us to start building Leap on top.
My plan would be to have a first Alpha end of May based on 42.1 sources with the SLE bits updated to SP2. The next snapshot should be before OSC in June and another one in July. I'd aim for the the first Beta last week of August, followed by Beta2 around September 21st. RC1 would then be Oct 6, followed by RC2 Oct 18. GM Oct 27 so we can release November 2nd.
cu Ludwig
Thank you for the info and heads up. Is there a possiblity to get a list of the "upgraded SLE 12 SP2" packages (versiondiff SLE 12 SP1/Leap42.1 <-> SP2) that will hit Leap 42.2? Otherwise, I'd like to call out to all interrested parties, for proposals of: 1. of upgrades in package versions for 42.2 2. added packages to 42.2 (new, replacement for, ...) 3. removal of packages from 42.2, (EOL, replaced by, ...) In this spirit, I'd like to propose the upgrade for the "docker" packages from 1.9.x to whatever is upstream stable (1.10.x atm) from the "Virtualization:containers" repo. - Yamaban.
Yamaban wrote:
On Mon, 21 Mar 2016 11:14, Ludwig Nussel wrote:
Time flies, so let's start planning the schedule for Leap 42.2. The current version 42.1 is based on SLE12 SP1 and 42.2 is meant to be based on SP2¹. SLE12 SP2 is expected to reach the beta phase mid of May which means we'll get the package sources in OBS then. That in turn will allow us to start building Leap on top.
My plan would be to have a first Alpha end of May based on 42.1 sources with the SLE bits updated to SP2. The next snapshot should be before OSC in June and another one in July. I'd aim for the the first Beta last week of August, followed by Beta2 around September 21st. RC1 would then be Oct 6, followed by RC2 Oct 18. GM Oct 27 so we can release November 2nd. [...] Thank you for the info and heads up.
Is there a possiblity to get a list of the "upgraded SLE 12 SP2" packages (versiondiff SLE 12 SP1/Leap42.1 <-> SP2) that will hit Leap 42.2?
The SP2 sources will be available in OBS in May so from then on it's possible to diff against 42.1. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi, Am 21.03.2016 um 13:43 schrieb Yamaban:
Otherwise, I'd like to call out to all interrested parties, for proposals of: 1. of upgrades in package versions for 42.2 2. added packages to 42.2 (new, replacement for, ...) 3. removal of packages from 42.2, (EOL, replaced by, ...)
Now since I finally had the time to look at packages which are interesting to me and my usecase. Can we as a maintainer group agree, that we do not want to discuss every single update request on the list which the above seems to imply? We have OBS and AFAIK it handles the case correctly when a package update is submitted from a non-maintainer that it'll automatically insert a review request to the actual maintainer. If that is the case I propose at least to handle "simple" upgrade and insertion requests like this. What is "simple" in the end is not always easy to decide and if in doubt this should be discussed between the requester and the maintainer or if it even has a bigger impact and no agreement we should bring it to this list probably. Can we agree on this simplification or is this already written in some process I missed? We can also define something else if necessary but using existing tools might help to improve efficiency. Another thing I'm wondering about is how to easily monitor updates to 42.2 which are either "forks" or pulled in from Factory (compared to updates automatically pulled in from SLES12 and 42.1 updates). Because I think it makes a lot of sense to have as many eyes as possible on those updates to assess if the upgrade path from 42.1 to 42.2 stays feasible as we try to position Leap 42 as some kind of LTS (similar to SLES service packs). Currently I see https://build.opensuse.org/package/view_file/openSUSE:Leap:42.2/00Meta/looku... as a snapshot which is not too easy to work with. So question to Ludwig who does a great job with the "New Tumbleweed snapshot XXX released": Would it be possible and feasible to have something similar for the ongoing 42.2 work? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Wolfgang Rosenauer schrieb:
Am 21.03.2016 um 13:43 schrieb Yamaban:
Otherwise, I'd like to call out to all interrested parties, for proposals of: 1. of upgrades in package versions for 42.2 2. added packages to 42.2 (new, replacement for, ...) 3. removal of packages from 42.2, (EOL, replaced by, ...)
Now since I finally had the time to look at packages which are interesting to me and my usecase.
Can we as a maintainer group agree, that we do not want to discuss every single update request on the list which the above seems to imply?
We have OBS and AFAIK it handles the case correctly when a package update is submitted from a non-maintainer that it'll automatically insert a review request to the actual maintainer. If that is the case I propose at least to handle "simple" upgrade and insertion requests like this.
What is "simple" in the end is not always easy to decide and if in doubt this should be discussed between the requester and the maintainer or if it even has a bigger impact and no agreement we should bring it to this list probably.
Can we agree on this simplification or is this already written in some process I missed?
Thanks for bringing the topic up! It's not OBS itself which decides whether to ask the maintainer but a quickly hacked bot that combines the maintenance bot and the factory source checker used by backports: https://github.com/openSUSE/osc-plugin-factory/blob/master/leaper.py The bot adds the Factory package maintainer as reviewer if the package exists in Factory. It also checks whether the origin of the package according to the lookup file changes (in a far too simple way). The bot adds me as fallback reviewer way too often. So I'd appreciate a good policy and maybe a leap review team the bot can use as fallback. I don't want to be the fallback reviewer. Wrt documentation so far we have https://en.opensuse.org/openSUSE:How_to_contribute_to_Leap but that's about it.
Another thing I'm wondering about is how to easily monitor updates to 42.2 which are either "forks" or pulled in from Factory (compared to updates automatically pulled in from SLES12 and 42.1 updates).
Because I think it makes a lot of sense to have as many eyes as possible on those updates to assess if the upgrade path from 42.1 to 42.2 stays feasible as we try to position Leap 42 as some kind of LTS (similar to SLES service packs).
The aforementioned bot at least knows where a package comes from. So it could do whatever one implements with that information :-) And there's also https://github.com/openSUSE/osc-plugin-factory/blob/master/manager_42.py which keeps the lookup file up to date. It could of course also be extended to create some sort of notification or summary. Right now it's stateless though so sending it's raw output would become annoying quite quickly.
Currently I see https://build.opensuse.org/package/view_file/openSUSE:Leap:42.2/00Meta/looku... as a snapshot which is not too easy to work with.
So question to Ludwig who does a great job with the "New Tumbleweed snapshot XXX released": Would it be possible and feasible to have something similar for the ongoing 42.2 work?
That script works on the DVD. At that point it doesn't have the origin information. It could of course send diffs between Leap builds, I'm not sure that's so useful right now though. Especially since Leap doesn't use the "totest" throttling mechanism of Tumbleweed. So ISOs are published when OBS releases them rather then when openQA considers them good. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/06/2016 15:09, Ludwig Nussel wrote:
Wrt documentation so far we have https://en.opensuse.org/openSUSE:How_to_contribute_to_Leap but that's about it. I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335. SLES has a different %suse_version for SP2. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dave Plater <dplater.list@gmail.com> Fri, 17 Jun 2016 19:29:18 +0300:
On 17/06/2016 15:09, Ludwig Nussel wrote:
Wrt documentation so far we have https://en.opensuse.org/openSUSE:How_to_contribute_to_Leap but that's about it. I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335. SLES has a different %suse_version for SP2. Dave P
Leap 42.2 will provide almost the same packages as 42.1 and even 13.2 f.e. gcc48 etc. %suse_version > 1320 will cause unneeded build errors imho. -- Best regards, Dmitriy Perlow R&D chemical engineer Lekpharm JLLC -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/06/2016 19:20, Dmitriy Perlow wrote:
Dave Plater <dplater.list@gmail.com> Fri, 17 Jun 2016 19:29:18 +0300:
On 17/06/2016 15:09, Ludwig Nussel wrote:
Wrt documentation so far we have https://en.opensuse.org/openSUSE:How_to_contribute_to_Leap but that's about it. I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335. SLES has a different %suse_version for SP2. Dave P
Leap 42.2 will provide almost the same packages as 42.1 and even 13.2 f.e. gcc48 etc. %suse_version > 1320 will cause unneeded build errors imho.
So openSUSE:Leap42.2 will become a stagnated distribution with no actual need to update from 42.1? What is the actual purpose of Leap? It's certainly going away from the old openSUSE distributions. My internet is expensive and my pockets are lean so I can't afford to run a bleeding edge Tumbleweed nor can I afford the time to fix breakages. I will eventually end up not being able to maintain most of my packages nor fix bugs for them properly. I'm already unable to install blender because it now only runs on python3-3.5. This situation will eventually force the use of snap packages as discussed in another thread. I use Leap and I'm happy with it and have been with openSUSE for quite a while. The first linux distribution I installed was 6.4 IIRC and I became actively involved in 10.1 but now I feel as if I'm being pushed away. I was looking forward to Leap:42.2 because I can't update python3 from 3.4 to 3.5 as too many packages depend upon it. It's been in Tumbleweed for a couple of months now, how long does it take to consider it stable. Gcc can stay at 48 as can most of the base packages. I don't care about the kernel either, I can't afford new hardware anyway. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Dave Plater <dplater.list@gmail.com> Fri, 17 Jun 2016 21:15:01 +0300:
On 17/06/2016 19:20, Dmitriy Perlow wrote:
Dave Plater <dplater.list@gmail.com> Fri, 17 Jun 2016 19:29:18 +0300:
On 17/06/2016 15:09, Ludwig Nussel wrote:
Wrt documentation so far we have https://en.opensuse.org/openSUSE:How_to_contribute_to_Leap but that's about it. I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335. SLES has a different %suse_version for SP2. Dave P
Leap 42.2 will provide almost the same packages as 42.1 and even 13.2 f.e. gcc48 etc. %suse_version > 1320 will cause unneeded build errors imho.
So openSUSE:Leap42.2 will become a stagnated distribution with no actual need to update from 42.1? What is the actual purpose of Leap? It's certainly going away from the old openSUSE distributions. My internet is expensive and my pockets are lean so I can't afford to run a bleeding edge Tumbleweed nor can I afford the time to fix breakages. I will eventually end up not being able to maintain most of my packages nor fix bugs for them properly. I'm already unable to install blender because it now only runs on python3-3.5. This situation will eventually force the use of snap packages as discussed in another thread. I use Leap and I'm happy with it and have been with openSUSE for quite a while. The first linux distribution I installed was 6.4 IIRC and I became actively involved in 10.1 but now I feel as if I'm being pushed away. I was looking forward to Leap:42.2 because I can't update python3 from 3.4 to 3.5 as too many packages depend upon it. It's been in Tumbleweed for a couple of months now, how long does it take to consider it stable. Gcc can stay at 48 as can most of the base packages. I don't care about the kernel either, I can't afford new hardware anyway.
Dave P
As for me new software releases require C++14 and at least gcc 4.9 with clang or clean gcc 5+. For example a month ago leechcraft package got the last update for distributions with gcc 4.8. Now dirty hacks at OBS are required to use not default compiler. Of course this crunch is available only for home projects. There will no be any update for 13.1-leap42 from oss & network. LC is my favorite desktop app that is why leap can't be my favorite desktop distribution. On the other hand I have nvidia card, noveau is bugware for me and I don't like nvidia run installers. That is why TW also can't be my favorite desktop distribution. -- Best regards, Dmitriy Perlow R&D chemical engineer Lekpharm JLLC -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Fri, Jun 17, 2016 at 2:15 PM, Dave Plater <dplater.list@gmail.com> wrote:
On 17/06/2016 19:20, Dmitriy Perlow wrote:
Dave Plater <dplater.list@gmail.com> Fri, 17 Jun 2016 19:29:18 +0300:
On 17/06/2016 15:09, Ludwig Nussel wrote:
Wrt documentation so far we have https://en.opensuse.org/openSUSE:How_to_contribute_to_Leap but that's about it.
I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335. SLES has a different %suse_version for SP2. Dave P
Leap 42.2 will provide almost the same packages as 42.1 and even 13.2 f.e. gcc48 etc. %suse_version > 1320 will cause unneeded build errors imho.
So openSUSE:Leap42.2 will become a stagnated distribution with no actual need to update from 42.1? What is the actual purpose of Leap? It's certainly going away from the old openSUSE distributions. My internet is expensive and my pockets are lean so I can't afford to run a bleeding edge Tumbleweed nor can I afford the time to fix breakages. I will eventually end up not being able to maintain most of my packages nor fix bugs for them properly. I'm already unable to install blender because it now only runs on python3-3.5. This situation will eventually force the use of snap packages as discussed in another thread. I use Leap and I'm happy with it and have been with openSUSE for quite a while. The first linux distribution I installed was 6.4 IIRC and I became actively involved in 10.1 but now I feel as if I'm being pushed away. I was looking forward to Leap:42.2 because I can't update python3 from 3.4 to 3.5 as too many packages depend upon it. It's been in Tumbleweed for a couple of months now, how long does it take to consider it stable. Gcc can stay at 48 as can most of the base packages. I don't care about the kernel either, I can't afford new hardware anyway.
Dave P
This will be interesting to see how 42.2 evolves from 42.1 First the "core" of 42.1 came from SLE 12, but that is only 1/3rd of the packages. The other 2/3rds are non-core and came from Tumbleweed a year ago. I expect that 2/3rds will get bumped up to Tumbleweed levels, but each maintainer will have to make that decision. And if they want the update, they will have to make a proactive effort to issue an SR from Tumbleweed (factory) to Leap 42.2. Will the python3 maintainer bump python to python 3.5 for Leap 42.2? No idea. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335. SLES has a different %suse_version for SP2.
no , SLE12 ,SP1 and SP2 have suse_version = 1315 , and sles_version = 120000 , 120100 and 120200 + Leap has defined is_opensuse = 1 On 17 June 2016 at 18:29, Dave Plater <dplater.list@gmail.com> wrote:
On 17/06/2016 15:09, Ludwig Nussel wrote:
Wrt documentation so far we have https://en.opensuse.org/openSUSE:How_to_contribute_to_Leap but that's about it.
I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335. SLES has a different %suse_version for SP2. Dave P
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 17/06/2016 23:45, Ondřej Súkup wrote:
I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335.
SLES has a different %suse_version for SP2. no , SLE12 ,SP1 and SP2 have suse_version = 1315 , and sles_version = 120000 , 120100 and 120200 + Leap has defined is_opensuse = 1
Exactly what my point is, you can distinguish between SLE12 SP1 and SP2 but you cannot distinguish between Leap:42.1 and 42.2 ie. %if %sles_version > 120100 identifies SP 2 only but there is no macro to identify Leap:42.2. Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
18.06.2016 08:10, Dave Plater пишет:
On 17/06/2016 23:45, Ondřej Súkup wrote:
I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335.
SLES has a different %suse_version for SP2. no , SLE12 ,SP1 and SP2 have suse_version = 1315 , and sles_version = 120000 , 120100 and 120200 + Leap has defined is_opensuse = 1
Exactly what my point is, you can distinguish between SLE12 SP1 and SP2 but you cannot distinguish between Leap:42.1 and 42.2 ie. %if %sles_version > 120100 identifies SP 2 only but there is no macro to identify Leap:42.2.
Now read message you responded to once more. %sles_version == 120200 && %is_opensuse == 1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 18/06/2016 07:13, Andrei Borzenkov wrote:
18.06.2016 08:10, Dave Plater пишет:
On 17/06/2016 23:45, Ondřej Súkup wrote:
I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335.
SLES has a different %suse_version for SP2. no , SLE12 ,SP1 and SP2 have suse_version = 1315 , and sles_version = 120000 , 120100 and 120200 + Leap has defined is_opensuse = 1
Exactly what my point is, you can distinguish between SLE12 SP1 and SP2 but you cannot distinguish between Leap:42.1 and 42.2 ie. %if %sles_version > 120100 identifies SP 2 only but there is no macro to identify Leap:42.2.
Now read message you responded to once more.
%sles_version == 120200 && %is_opensuse == 1
I'm confused, on my Leap:42.1 system rpm --eval %sles_version 0 %suse_version evaluates to 1315 %is_opensuse evaluates to 1, if Leap42.2 has a sles_version of 0 as well then there is no way to inform rpmbuild whether it is building for Leap:42.1 or 42.2 or are you stating that Leap:42.2 will have a sles_version as well as a suse_version? I apologize if you were agreeing with my first statement, there are many english languages in this world and it's difficult to understand them all. Dave -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
18.06.2016 08:26, Dave Plater пишет:
On 18/06/2016 07:13, Andrei Borzenkov wrote:
18.06.2016 08:10, Dave Plater пишет:
On 17/06/2016 23:45, Ondřej Súkup wrote:
I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335.
SLES has a different %suse_version for SP2. no , SLE12 ,SP1 and SP2 have suse_version = 1315 , and sles_version = 120000 , 120100 and 120200 + Leap has defined is_opensuse = 1
Exactly what my point is, you can distinguish between SLE12 SP1 and SP2 but you cannot distinguish between Leap:42.1 and 42.2 ie. %if %sles_version > 120100 identifies SP 2 only but there is no macro to identify Leap:42.2.
Now read message you responded to once more.
%sles_version == 120200 && %is_opensuse == 1
I'm confused, on my Leap:42.1 system rpm --eval %sles_version 0 %suse_version evaluates to 1315 %is_opensuse evaluates to 1, if Leap42.2 has a sles_version of 0 as well then there is no way to inform rpmbuild whether it is building for Leap:42.1 or 42.2 or are you stating that Leap:42.2 will have a sles_version as well as a suse_version? I apologize if you were agreeing with my first statement, there are many english languages in this world and it's difficult to understand them all.
That is a mess, really :( First, this is not %sles_version, this is %sle_version. See https://lists.opensuse.org/opensuse-factory/2015-07/msg00815.html Second, this appears to be defined for OBS project only but missing in RPM macros. See e.g. https://build.opensuse.org/project/prjconf/openSUSE:Leap:42.1 Macros: %sle_version 120100 %suse_version 1315 %is_opensuse 1 :Macros Finally there was discussion about adding %leap_version http://comments.gmane.org/gmane.linux.suse.opensuse.packaging/14660 And according to the last rpm changelog entry in Leap 42.1 it was also added ... except it is missing. https://bugzilla.opensuse.org/show_bug.cgi?id=985527 It is present in RPM in Leap 42.2 but I do not know if it has any meaningful value there: sed -e 's/@suse_version@/%{?suse_version}%{!?suse_version:0}/' \ -e 's/@sles_version@/%{?sles_version}%{!?sles_version:0}/' \ -e 's/@ul_version@/%{?ul_version}%{!?ul_version:0}/' \ -e '/@is_opensuse@%{?is_opensuse:nomatch}/d' \ -e 's/@is_opensuse@/%{?is_opensuse}%{!?is_opensuse:0}/' \ -e '/@leap_version@%{?leap_version:nomatch}/d' \ -e 's/@leap_version@/%{?leap_version}%{!?leap_version:0}/' \ < %{SOURCE4} > suse_macros So it sounds like catch 22 - we need valid %leap_version to set %leap_version. And where valid %leap_version comes from? And RPM macros still have no trace of %sle_version ... OMG ... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
18.06.2016 08:26, Dave Plater пишет:
On 18/06/2016 07:13, Andrei Borzenkov wrote:
18.06.2016 08:10, Dave Plater пишет:
On 17/06/2016 23:45, Ondřej Súkup wrote:
I just read the link and at the bottom it states that both openSUSE:Leap:42.1 and 42.2 will be %suse_version 1315, is this intended? Can't Leap:42.2 at least be 1316 or better still 1335. > SLES has a different %suse_version for SP2. no , SLE12 ,SP1 and SP2 have suse_version = 1315 , and sles_version = 120000 , 120100 and 120200 + Leap has defined is_opensuse = 1
Exactly what my point is, you can distinguish between SLE12 SP1 and SP2 but you cannot distinguish between Leap:42.1 and 42.2 ie. %if %sles_version > 120100 identifies SP 2 only but there is no macro to identify Leap:42.2.
Now read message you responded to once more.
%sles_version == 120200 && %is_opensuse == 1
I'm confused, on my Leap:42.1 system rpm --eval %sles_version 0 %suse_version evaluates to 1315 %is_opensuse evaluates to 1, if Leap42.2 has a sles_version of 0 as well then there is no way to inform rpmbuild whether it is building for Leap:42.1 or 42.2 or are you stating that Leap:42.2 will have a sles_version as well as a suse_version? I apologize if you were agreeing with my first statement, there are many english languages in this world and it's difficult to understand them all.
That is a mess, really :(
First, this is not %sles_version, this is %sle_version. See
https://lists.opensuse.org/opensuse-factory/2015-07/msg00815.html Thanks for the heads up, I only came back on line with the mailing lists at the end of 2015, prior to that I had to depend on web gmail.
Second, this appears to be defined for OBS project only but missing in RPM macros. See e.g. https://build.opensuse.org/project/prjconf/openSUSE:Leap:42.1
Macros: %sle_version 120100 %suse_version 1315 %is_opensuse 1 :Macros
Finally there was discussion about adding %leap_version
http://comments.gmane.org/gmane.linux.suse.opensuse.packaging/14660 At least the ffmpeg problem was resolved, it's now only maintained in multimedia:libs and linked, along with other mission critical libraries
On 18/06/2016 09:19, Andrei Borzenkov wrote: like gstreamer. This has solved most of the old volatility of Packman packages and the mailing list is quiet. I think the shift in maintainers had something to do with Stephan not keeping his promise, sle_version works for me anyway.
And according to the last rpm changelog entry in Leap 42.1 it was also added ... except it is missing.
https://bugzilla.opensuse.org/show_bug.cgi?id=985527
It is present in RPM in Leap 42.2 but I do not know if it has any meaningful value there:
sed -e 's/@suse_version@/%{?suse_version}%{!?suse_version:0}/' \ -e 's/@sles_version@/%{?sles_version}%{!?sles_version:0}/' \ -e 's/@ul_version@/%{?ul_version}%{!?ul_version:0}/' \ -e '/@is_opensuse@%{?is_opensuse:nomatch}/d' \ -e 's/@is_opensuse@/%{?is_opensuse}%{!?is_opensuse:0}/' \ -e '/@leap_version@%{?leap_version:nomatch}/d' \ -e 's/@leap_version@/%{?leap_version}%{!?leap_version:0}/' \ < %{SOURCE4} > suse_macros
So it sounds like catch 22 - we need valid %leap_version to set %leap_version. And where valid %leap_version comes from?
The path of least resistance is to replace leap_version with sle_version but sle_version doesn't make sense it should be leap_version at least is_opensuse gets set. I sense that there is some conflict behind the scenes in the land of enterprise suse. We'll wait and see what comes of your bug.
And RPM macros still have no trace of %sle_version ...
OMG ...
Thanks again, I have sle_version to distinguish 42.1 and 42.2, I just confirmed with osc meta prjconf openSUSE:Leap:42.2|grep sle_version. I can always define it locally myself like I do with BUILD_ORIG. My confusion came with sle_version and sles_version. Thanks Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hello, On Jun 17 13:52 Wolfgang Rosenauer wrote (excerpt):
We have OBS and AFAIK it handles the case correctly when a package update is submitted from a non-maintainer that it'll automatically insert a review request to the actual maintainer. If that is the case I propose at least to handle "simple" upgrade and insertion requests like this.
What is "simple" in the end is not always easy to decide
FYI: You may have a look at https://en.opensuse.org/openSUSE:How_to_contribute_to_the_Printing_project what a "simple version upgrade" is from my point of view. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 21/03/2016 12:14, Ludwig Nussel wrote:
Hi,
Time flies, so let's start planning the schedule for Leap 42.2. The current version 42.1 is based on SLE12 SP1 and 42.2 is meant to be based on SP2¹. SLE12 SP2 is expected to reach the beta phase mid of May which means we'll get the package sources in OBS then. That in turn will allow us to start building Leap on top.
My plan would be to have a first Alpha end of May based on 42.1 sources with the SLE bits updated to SP2. The next snapshot should be before OSC in June and another one in July. I'd aim for the the first Beta last week of August, followed by Beta2 around September 21st. RC1 would then be Oct 6, followed by RC2 Oct 18. GM Oct 27 so we can release November 2nd.
cu Ludwig
A silly question, will packages already in Leap:42.1 be included in Leap:42.2? Regards Dave P -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
Andrei Borzenkov -
Dave Plater -
Dmitriy Perlow -
Greg Freemyer -
Johannes Meixner -
Ludwig Nussel -
Ondřej Súkup -
Wolfgang Rosenauer -
Yamaban