Bug 1737108 - Breaking change in behaviour without prior notice !
Summary: Breaking change in behaviour without prior notice !
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: scons
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mosaab Alzoubi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-02 16:40 UTC by Michal Schorm
Modified: 2019-08-02 18:35 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-02 18:35:56 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Michal Schorm 2019-08-02 16:40:39 UTC
On Fedora rawhide (31), the "scons-3" command can't be called anymore.

As far as I understood, the "/usr/bin/scons-3" was renamed to "/usr/bin/scons".

Since it is a make tool, you broke all packages that were building themselves by calling "scons-3".
E.g. "galera".

--

I'm fine with the change itself, but you should have done one or more from following:
* Propose a F31 self-contained change
* Inform on the fedora-devel mailing list
* File BZs against the affected projects
* file PRs against the affected projects with correct solution

--

I only get notified by rel-engs because my package FTBFS on F31 mass rebuild.

In case that was not intended change, you now know.
In case it was - what's the correct use now? Just calling "scons" ?
(then it's OK to close this BZ)

Comment 1 Michal Schorm 2019-08-02 16:47:29 UTC
I guess it makes more sense to use "scons" than "scons-3.7", since it will bump to "scons-3.8" after: https://fedoraproject.org/wiki/Changes/Python3.8
Right?

Comment 2 Antonio T. (sagitter) 2019-08-02 17:26:18 UTC

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/AFKGFBXU74TZDPQA5PXGUI4MBIWILUR7/(In reply to Michal Schorm from comment #0)
> On Fedora rawhide (31), the "scons-3" command can't be called anymore.
> 
> As far as I understood, the "/usr/bin/scons-3" was renamed to
> "/usr/bin/scons".

Exactly, because of the migration to Python3.

> 
> Since it is a make tool, you broke all packages that were building
> themselves by calling "scons-3".
> E.g. "galera".
> 

It was predictable:

Was Tuesday, Jul 23 2019 on Fedora devel mailing list:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/AFKGFBXU74TZDPQA5PXGUI4MBIWILUR7/

Was Friday, August 2018 on Fedora devel mailing list:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/XMZGWJ7MBKHB7U7ZSOVCXZUHEBL62M7W/

> --
> 
> I'm fine with the change itself, but you should have done one or more from
> following:
> * Propose a F31 self-contained change
> * Inform on the fedora-devel mailing list
> * File BZs against the affected projects
> * file PRs against the affected projects with correct solution
> 
> --
> 
> I only get notified by rel-engs because my package FTBFS on F31 mass rebuild.
> 
> In case that was not intended change, you now know.
> In case it was - what's the correct use now? Just calling "scons" ?
> (then it's OK to close this BZ)

'scons' was (Fedora < 31) a Python2 command. If you need to manage Python3 code you need to use 'scons-3*'.

For effect of the migration to Python3 on Fedora,

'scons' is now (on Fedora 31+) a Python3 command. If you need to manage Python3 code you need to use 'scons-2*'.

On EPEL,

'scons' is still a Python2 command like happened on Fedora < 31.

Comment 3 Antonio T. (sagitter) 2019-08-02 17:27:56 UTC
>'scons' is now (on Fedora 31+) a Python3 command. If you need to manage Python3 code you need to use 'scons-2*'.

Sorry, i meant

'scons' is now (on Fedora 31+) a Python3 command. If you need to manage Python2 code you need to use 'scons-2*'.

Comment 4 Michal Schorm 2019-08-02 17:40:05 UTC
Okay, thanks for explanation.

I fixed the galera package with:
https://src.fedoraproject.org/rpms/galera/c/10f9bc2546dbca48532af1578563ababecc5a07c?branch=master

--

I'm fine with closing this BZ now :)


Note You need to log in before you can comment on or make changes to this bug.