potiuk opened a new pull request, #55151:
URL: https://github.com/apache/airflow/pull/55151

   After migrating to python built from sources, it turned out that we had a 
weird mixture of system and source build python in our CI images images. There 
were some dependencies installed that installed python3 debian dependencies and 
they were breaking the way how source build python 3.11 interacted with system 
one. Namely - debian Python 3.11 had internal ABI incompatibility between 
3.11.4 and 3.11.5 that caused the ssl build with latest 3.11.5 fail when 3.11.5 
system python has been installed while the new python was being built - because 
system includes interfered with the build process.
   
   The system python was pulled by "software-properties-common" and "gdb" - we 
do not need to use either of them during the build process, and user in
   
   In order to avoid this, we now make sure that we do not install any debian 
dependencies that pull any of the python3 system packages, before we install 
Python from sources.
   
   We also reviewed and cleaned the way how we configure list of packages 
installed during image building:
   
   * packages are reviewed and unnecessary ones removed
   * packages that are pulling python3 system packages are moved to additional 
apt dev dependencies
   * additional apt dev dependencies are installed AFTER python is installed
   * the packages listed in scripts are now one-per-line
   * they are alphabetically sorted
   * finally LD_LIBRARY_PATH is set to have the "source-installed" python 
libraries to be always prioritised against the system libraries if system 
libraries are installed to the main "/usr/lib" directories.
   
   <!--
    Licensed to the Apache Software Foundation (ASF) under one
    or more contributor license agreements.  See the NOTICE file
    distributed with this work for additional information
    regarding copyright ownership.  The ASF licenses this file
    to you under the Apache License, Version 2.0 (the
    "License"); you may not use this file except in compliance
    with the License.  You may obtain a copy of the License at
   
      http://www.apache.org/licenses/LICENSE-2.0
   
    Unless required by applicable law or agreed to in writing,
    software distributed under the License is distributed on an
    "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
    KIND, either express or implied.  See the License for the
    specific language governing permissions and limitations
    under the License.
    -->
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of an existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   
   
   <!-- Please keep an empty line above the dashes. -->
   ---
   **^ Add meaningful description above**
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to