Hi all,
since 42.3 officially reached its end of life on Monday I'll go ahead and remove the Repo from the xfce Project tomorrow unless there are any objections.
Am Mittwoch, 3. Juli 2019, 11:54:01 CEST schrieb Marcel Kühlhorn:
Hi all,
since 42.3 officially reached its end of life on Monday I'll go ahead and remove the Repo from the xfce Project tomorrow unless there are any objections.
No objections at all, even more as X11:xfce is the development repository.
Regards, vinz.
Moin,
On Wed, 03 Jul 2019, 13:15:54 +0200, Vinzenz Vietzke wrote:
Am Mittwoch, 3. Juli 2019, 11:54:01 CEST schrieb Marcel Kühlhorn:
Hi all,
since 42.3 officially reached its end of life on Monday I'll go ahead and remove the Repo from the xfce Project tomorrow unless there are any objections.
No objections at all, even more as X11:xfce is the development repository.
while this is true in principle, I see it a little different... Background: I have to maintain quite a few desktops, workstations, .. here (remotely), which I don't want to migrate to 15.0... due to several reasons: (a) 15.0 is a .0 release after all, and I really hate the situation that rebooting or shutting it down hangs for whatever reason, and (b) 15.1 hasn't been able to show that this particular issue is actually solved.
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly. FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable ;)
TIA, cheers.
l8er manfred
Am Mittwoch, 3. Juli 2019, 14:33:22 CEST schrieb Manfred Hollstein:
while this is true in principle, I see it a little different... Background: I have to maintain quite a few desktops, workstations, .. here (remotely), which I don't want to migrate to 15.0... due to several reasons: 15.0 is a .0 release after all, and I really hate the situation that rebooting or shutting it down hangs for whatever reason, and (b) 15.1 hasn't been able to show that this particular issue is actually solved.
So you don't migrate to a new major release for stability reasons - but you use a devel repository? Sounds odd to me.
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly. FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable
You could fork the current X11:xfce to your OBS home project. That gives you full control and you can keep it as long as you need it.
Regards, vinz.
Hi Vinz,
On Wed, 03 Jul 2019, 15:57:54 +0200, Vinzenz Vietzke wrote:
Am Mittwoch, 3. Juli 2019, 14:33:22 CEST schrieb Manfred Hollstein:
while this is true in principle, I see it a little different... Background: I have to maintain quite a few desktops, workstations, .. here (remotely), which I don't want to migrate to 15.0... due to several reasons: 15.0 is a .0 release after all, and I really hate the situation that rebooting or shutting it down hangs for whatever reason, and (b) 15.1 hasn't been able to show that this particular issue is actually solved.
So you don't migrate to a new major release for stability reasons - but you use a devel repository? Sounds odd to me.
well, may sound odd, but when you're following the development of the repo, one can estimate, if it's a risk or adds additional value...
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly. FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable
You could fork the current X11:xfce to your OBS home project. That gives you full control and you can keep it as long as you need it.
Good idea, I'll just do that :)
Regards, vinz.
Cheers.
l8er manfred
Hi Manfred,
On 7/3/19 10:42 PM, Manfred Hollstein wrote:
So you don't migrate to a new major release for stability reasons - but you use a devel repository? Sounds odd to me.
well, may sound odd, but when you're following the development of the repo, one can estimate, if it's a risk or adds additional value...
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly. FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable
You could fork the current X11:xfce to your OBS home project. That gives you full control and you can keep it as long as you need it.
Good idea, I'll just do that :)
Yes it would be a good idea for you to start forking what you need and we can give you time to do so. We will start updating Xfce to 4.14 soon (official release in August) and it does not build for Leap 42.3. After the transition the all packages will be gone and the X11:xfce will be useless for your 42.3 machines.
Just let us know when you're done :)
Hi Maurizio,
On Wed, 03 Jul 2019, 17:04:36 +0200, Maurizio Galli (MauG) wrote:
Hi Manfred,
On 7/3/19 10:42 PM, Manfred Hollstein wrote:
So you don't migrate to a new major release for stability reasons - but you use a devel repository? Sounds odd to me.
well, may sound odd, but when you're following the development of the repo, one can estimate, if it's a risk or adds additional value...
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly. FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable
You could fork the current X11:xfce to your OBS home project. That gives you full control and you can keep it as long as you need it.
Good idea, I'll just do that :)
Yes it would be a good idea for you to start forking what you need and we can give you time to do so. We will start updating Xfce to 4.14 soon (official release in August) and it does not build for Leap 42.3. After the transition the all packages will be gone and the X11:xfce will be useless for your 42.3 machines.
Just let us know when you're done :)
Done.
Cheers.
l8er manfred
Moin,
On Wed, 03 Jul 2019, 17:48:30 +0200, Manfred Hollstein wrote:
Hi Maurizio,
On Wed, 03 Jul 2019, 17:04:36 +0200, Maurizio Galli (MauG) wrote:
Hi Manfred,
On 7/3/19 10:42 PM, Manfred Hollstein wrote:
So you don't migrate to a new major release for stability reasons - but you use a devel repository? Sounds odd to me.
well, may sound odd, but when you're following the development of the repo, one can estimate, if it's a risk or adds additional value...
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly. FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable
You could fork the current X11:xfce to your OBS home project. That gives you full control and you can keep it as long as you need it.
Good idea, I'll just do that :)
Yes it would be a good idea for you to start forking what you need and we can give you time to do so. We will start updating Xfce to 4.14 soon (official release in August) and it does not build for Leap 42.3. After the transition the all packages will be gone and the X11:xfce will be useless for your 42.3 machines.
Just let us know when you're done :)
Done.
well, I only say %make_build, which has been added as some openSUSE specific macro, *without* having been defined for elder versions...
%if 0%{?suse_version} > 1320 %make_build %else %make %{?_smp_mflags} %endif
I tend to agree with some people from the "please someone help with SR#711379" thread; using openSUSE specific macros *which only work in a specifc release* *is stupid*!
Cheers.
l8er manfred
On Wed, 03 Jul 2019, 18:39:21 +0200, Manfred Hollstein wrote:
Moin,
On Wed, 03 Jul 2019, 17:48:30 +0200, Manfred Hollstein wrote:
Hi Maurizio,
On Wed, 03 Jul 2019, 17:04:36 +0200, Maurizio Galli (MauG) wrote:
Hi Manfred,
On 7/3/19 10:42 PM, Manfred Hollstein wrote:
So you don't migrate to a new major release for stability reasons - but you use a devel repository? Sounds odd to me.
well, may sound odd, but when you're following the development of the repo, one can estimate, if it's a risk or adds additional value...
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly. FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable
You could fork the current X11:xfce to your OBS home project. That gives you full control and you can keep it as long as you need it.
Good idea, I'll just do that :)
Yes it would be a good idea for you to start forking what you need and we can give you time to do so. We will start updating Xfce to 4.14 soon (official release in August) and it does not build for Leap 42.3. After the transition the all packages will be gone and the X11:xfce will be useless for your 42.3 machines.
Just let us know when you're done :)
Done.
well, I only say %make_build, which has been added as some openSUSE specific macro, *without* having been defined for elder versions...
%if 0%{?suse_version} > 1320 %make_build %else %make %{?_smp_mflags} %endif
Oh well, even "%make" is not known... Changing it into a plain "make".
I tend to agree with some people from the "please someone help with SR#711379" thread; using openSUSE specific macros *which only work in a specifc release* *is stupid*!
Cheers.
l8er manfred
On 7/4/19 12:46 AM, Manfred Hollstein wrote:
On Wed, 03 Jul 2019, 18:39:21 +0200, Manfred Hollstein wrote:
Moin,
On Wed, 03 Jul 2019, 17:48:30 +0200, Manfred Hollstein wrote:
Hi Maurizio,
On Wed, 03 Jul 2019, 17:04:36 +0200, Maurizio Galli (MauG) wrote:
Hi Manfred,
On 7/3/19 10:42 PM, Manfred Hollstein wrote:
So you don't migrate to a new major release for stability reasons - but you use a devel repository? Sounds odd to me.
well, may sound odd, but when you're following the development of the repo, one can estimate, if it's a risk or adds additional value...
> I would really appreciate, if the 42.3 repo could be left _as it is_ for > some time, just to ensure new setups based on 15.1 will work properly. > FWIW, I really wouldn't mind to see new packages/version fail to build > for 42.3, but the one's which are there should remain installable
You could fork the current X11:xfce to your OBS home project. That gives you full control and you can keep it as long as you need it.
Good idea, I'll just do that :)
Yes it would be a good idea for you to start forking what you need and we can give you time to do so. We will start updating Xfce to 4.14 soon (official release in August) and it does not build for Leap 42.3. After the transition the all packages will be gone and the X11:xfce will be useless for your 42.3 machines.
Just let us know when you're done :)
Done.
well, I only say %make_build, which has been added as some openSUSE specific macro, *without* having been defined for elder versions...
%if 0%{?suse_version} > 1320 %make_build %else %make %{?_smp_mflags} %endif
Oh well, even "%make" is not known... Changing it into a plain "make".
Sorry Manfred, I read your email wrong and misunderstood you were talking about specific macros. Ignore my other email in reply to this.
Try the following: make %{?_smp_mflags} V=1
However it is sometimes a problem of Leap 42.3 no longer able to provide the required dependencies.
Am 03.07.19 um 14:33 schrieb Manfred Hollstein:
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly.> FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable ;)
If we disable building for 42.3 (but don't remove it), this will be the case. Binaries will stay as-is.
If we keep it enabled, some packages might build, others might fail and the whole repo state for 42.3 will be inconsistent, so that the risk of it being uninstallable are much higher.
I'd vote for keeping 42.3 build-disabled, but not removed for some months. It won't waste many resources that way and still be useful to some.
On Wed, 03 Jul 2019, 19:41:03 +0200, Stefan Seyfried wrote:
Am 03.07.19 um 14:33 schrieb Manfred Hollstein:
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly.> FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable ;)
If we disable building for 42.3 (but don't remove it), this will be the case. Binaries will stay as-is.
If we keep it enabled, some packages might build, others might fail and the whole repo state for 42.3 will be inconsistent, so that the risk of it being uninstallable are much higher.
I'd vote for keeping 42.3 build-disabled, but not removed for some months. It won't waste many resources that way and still be useful to some.
thx, Stefan! That's exactly what I wanted to achieve ;)
Cheers.
l8er manfred
On 7/4/19 1:41 AM, Stefan Seyfried wrote:
Am 03.07.19 um 14:33 schrieb Manfred Hollstein:
I would really appreciate, if the 42.3 repo could be left _as it is_ for some time, just to ensure new setups based on 15.1 will work properly.> FWIW, I really wouldn't mind to see new packages/version fail to build for 42.3, but the one's which are there should remain installable ;)
If we disable building for 42.3 (but don't remove it), this will be the case. Binaries will stay as-is.
If we keep it enabled, some packages might build, others might fail and the whole repo state for 42.3 will be inconsistent, so that the risk of it being uninstallable are much higher.
I'd vote for keeping 42.3 build-disabled, but not removed for some months. It won't waste many resources that way and still be useful to some.
Sounds reasonable to me.
Am Wed, 3 Jul 2019 19:41:03 +0200 schrieb Stefan Seyfried stefan.seyfried@googlemail.com:
If we disable building for 42.3 (but don't remove it), this will be the case. Binaries will stay as-is.
If we keep it enabled, some packages might build, others might fail and the whole repo state for 42.3 will be inconsistent, so that the risk of it being uninstallable are much higher.
I'd vote for keeping 42.3 build-disabled, but not removed for some months. It won't waste many resources that way and still be useful to some.
Ha, I wasn't aware of that being possible. Sounds good to me and I'd vote for that as well, as there might be others like Manfred relying on that repo. So we can even avoid duplications of the packages in various home repositories.
Regards, vinz.
-
Manfred Hollstein -
Marcel Kühlhorn -
Maurizio Galli (MauG) -
Stefan Seyfried -
Vinzenz Vietzke