PatrykKlimowicz commented on issue #25177:
URL: https://github.com/apache/airflow/issues/25177#issuecomment-1192328622

   @potiuk I followed 
[this](https://github.com/apache/airflow/blob/main/BREEZE.rst#installation) to 
setup env with breeze, but I stuck on this error:
   
   ```bash
   (myvenv) ➜  ~/dev/airflow  git:(main) ✗ breeze --force-build 
prepare-provider-packages elasticsearch --version-suffix-for-pypi post1
   Good version of Docker: 20.10.12.
   Good version of docker-compose: 2.2.3
   Good Docker context used: default.
   Docker image build is not needed for CI build as no important files are 
changed! You can add --force-build to force it
   Requirement already satisfied: pip==22.2 in 
/usr/local/lib/python3.7/site-packages (22.2)
   WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
   
   Get all providers
   
   
   Copy sources
   
   
===================================================================================
    Copying sources for provider packages
   
===================================================================================
   /opt/airflow /opt/airflow/dev/provider_packages
   /opt/airflow/dev/provider_packages
   
-----------------------------------------------------------------------------------
   
    Package Version of providers suffix set for PyPI version: post1
   
   
-----------------------------------------------------------------------------------
   ########## Generate setup files for 'elasticsearch' ##########
   Traceback (most recent call last):
     File "/opt/airflow/dev/provider_packages/prepare_provider_packages.py", 
line 2001, in <module>
       cli()
     File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1130, in 
__call__
       return self.main(*args, **kwargs)
     File "/usr/local/lib/python3.7/site-packages/rich_click/rich_group.py", 
line 21, in main
       rv = super().main(*args, standalone_mode=False, **kwargs)
     File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1055, in 
main
       rv = self.invoke(ctx)
     File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1657, in 
invoke
       return _process_result(sub_ctx.command.invoke(sub_ctx))
     File "/usr/local/lib/python3.7/site-packages/click/core.py", line 1404, in 
invoke
       return ctx.invoke(self.callback, **ctx.params)
     File "/usr/local/lib/python3.7/site-packages/click/core.py", line 760, in 
invoke
       return __callback(*args, **kwargs)
     File "/opt/airflow/dev/provider_packages/prepare_provider_packages.py", 
line 1541, in generate_setup_files
       current_tag = get_current_tag(provider_package_id, version_suffix, 
git_update, verbose)
     File "/opt/airflow/dev/provider_packages/prepare_provider_packages.py", 
line 1553, in get_current_tag
       make_sure_remote_apache_exists_and_fetch(git_update, verbose)
     File "/opt/airflow/dev/provider_packages/prepare_provider_packages.py", 
line 715, in make_sure_remote_apache_exists_and_fetch
       stderr=subprocess.DEVNULL,
     File "/usr/local/lib/python3.7/subprocess.py", line 363, in check_call
       raise CalledProcessError(retcode, cmd)
   subprocess.CalledProcessError: Command '['git', 'fetch', '--tags', 
'--force', 'apache-https-for-providers']' returned non-zero exit status 128.
   
===================================================================================
   
   Summary of prepared packages:
   
       Errors:
   elasticsearch
   
   
==================================================================================
   
==================================================================================
   
   There were errors when preparing packages. Exiting! 
   ```
   
   Any ideas? 


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