FDroid build error - pip3 command not found

1

Hi, started today, I have a build error. The same app with the same configuration yesterday was built successfully.

Do you have an idea what is the reason of this error?

Use 'apt autoremove' to remove them.

[141](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L141)0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

[142](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L142)$ test -n "$fdroidserver" || source /etc/profile.d/bsenv.sh

[143](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L143)$ git clone --depth=1 --branch=0.6.1 https://gitlab.com/fdroid/sdkmanager.git

[144](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L144)Cloning into 'sdkmanager'...

[145](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L145)Note: switching to 'f7e1064a78462a74cfc4ce3b1214c29644e438d7'.

[146](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L146)You are in 'detached HEAD' state. You can look around, make experimental

[147](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L147)changes and commit them, and you can discard any commits you make in this

[148](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L148)state without impacting any branches by switching back to a branch.

[149](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L149)If you want to create a new branch to retain commits you create, you may

[150](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L150)do so (now or later) by using -c with the switch command. Example:

[151](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L151) git switch -c <new-branch-name>

[152](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L152)Or undo this operation with:

[153](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L153) git switch -

[154](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L154)Turn off this advice by setting config variable advice.detachedHead to false

[155](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L155)$ git -C sdkmanager checkout -B master f7e1064a78462a74cfc4ce3b1214c29644e438d7

[156](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L156)Switched to a new branch 'master'

[157](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L157)$ pip3 install -e sdkmanager

[158](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L158)/bin/bash: line 171: pip3: command not found

[160](https://gitlab.com/dev354354/fdroiddata/-/jobs/3161088805#L160)Uploading artifacts for failed job
2

The CI should be fixed today, re-run

1 Like
3

Yep, now it works, thanks.

4

I’m getting this now (7 Nov.) Is the CI broken again, or are there changes required to my .yml file?

$ pip3 install -e sdkmanager

/bin/bash: line 171: pip3: command not found`

Thanks,

–Eric

1 Like
5

If the MR is old (before the fixes) you’d need to rebase first.

1 Like
6

Fun fact I started a build of xw4 now locally :slight_smile:

1 Like
7 
...
> Configure project :app
WARNING: Support for ANDROID_NDK_HOME is deprecated and will be removed in the future. Use android.ndkVersion in build.gradle instead.
Support for ANDROID_NDK_HOME is deprecated and will be removed in the future. Use android.ndkVersion in build.gradle instead.

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':app:lintVitalXw4fdroidRelease'.
> Could not resolve all artifacts for configuration ':app:xw4fdroidDebugCompileClasspath'.
   > Could not resolve androidx.core:core:1.0.+.
     Required by:
         project :app
      > Skipped due to earlier error
   > Could not resolve androidx.activity:activity:[1.2.2].
     Required by:
         project :app > androidx.activity:activity-ktx:1.2.2
      > Skipped due to earlier error

I just added make to the sudo: block, any thoughts?

1 Like
8

When I see errors about artifacts for configuration it’s usually something about servers the build system requires for android components: a problem on google’s end (?) that goes away eventually. I’m having local builds fail periodically with similar messages, then succeed a few seconds later when, I assume, my internet connection is behaving better.

1 Like
9

After adding make as you suggested, and waiting until my local builds stopped failing due to that artifact-resolution error, I kicked off another CI build. This time it got beyond that error and succeeded. Thanks! The pip3 error was fixed by catching up with upstream changes, as you said.

1 Like
10
1 Like
11

Thank You For The Data

12

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.