zachliu opened a new issue #15463:
URL: https://github.com/apache/airflow/issues/15463


   **Apache Airflow version**: 2.0.2
   
   **What happened**:
   
   Airflow's 2.0.2's [constraints 
file](https://raw.githubusercontent.com/apache/airflow/constraints-2.0.2/constraints-3.8.txt)
 has used newer `oauthlib==3.1.0` and `request-oauthlib==1.3.0` than 2.0.1's 
[constraints 
file](https://raw.githubusercontent.com/apache/airflow/constraints-2.0.1/constraints-3.8.txt)
   
   However both 2.0.2's 
[setup.py](https://github.com/apache/airflow/blob/10023fdd65fa78033e7125d3d8103b63c127056e/setup.py#L282-L286)
 and 2.0.1's 
[setup.py](https://github.com/apache/airflow/blob/beb8af5ac6c438c29e2c186145115fb1334a3735/setup.py#L273)
 don't allow these new versions
   
   Image build with `google_auth` being an "extra"  will fail if using 
`pip==21.0.1` **without** the `--use-deprecated=legacy-resolver` flag.
   
   Another option is to use `pip==20.2.4`.
   
   **What you expected to happen**:
   
   The package versions in `setup.py` and `constraints-3.8.txt` should be 
consistent with each other.
   
   <!-- What do you think went wrong? -->
   
   **How to reproduce it**:
   
   `docker build` with the following in the `Dockerfile`:
   ```
   pip install 
apache-airflow[password,celery,redis,postgres,hive,jdbc,mysql,statsd,ssh,google_auth]==2.0.2
 \
       --constraint 
https://raw.githubusercontent.com/apache/airflow/constraints-2.0.2/constraints-3.8.txt
   ```
   image build failed with
   
   ```
   ERROR: Could not find a version that satisfies the requirement 
oauthlib!=2.0.3,!=2.0.4,!=2.0.5,<3.0.0,>=1.1.2; extra == "google_auth" (from 
apache-airflow[celery,google-auth,hive,jdbc,mysql,password,postgres,redis,ssh,statsd])
   ERROR: No matching distribution found for 
oauthlib!=2.0.3,!=2.0.4,!=2.0.5,<3.0.0,>=1.1.2; extra == "google_auth"
   ```


-- 
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.

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


Reply via email to