Stop at 'Chosen extractor for .deb packages: ar' when 'directory' install to internal storage

[Houiin]

Android Q , Kernel version :4.9.232 Installation type: Directory Installation path : {EXTERNAL_STORAGE}/linux Busybox location : /system/xbin ; Version:v1.31.1-meefik

I have 'adb shell cmd appops set ru.meefik.linuxdeploy android:legacy_storage allow' and changed the path variable to /system/xbin in the settings and update env. Then I try to install Debian but stop at 'Chosen extractor for .deb packages: ar' every time.

If I use the file method (*.img ) to install or install in /data/{linux_deploy_folder}/files/linux , it works well.

[Sepero]

I also had this issue. I assume it is a problem with permissions. It's doesn't seem possible to chmod or chown anything on the storage.

[parke]

I am not a user of linuxdeploy, so the following information may or may not be relevant to your situation.

I encountered the same error message (Chosen extractor for .deb packages: ar) when running debootstrap manually in another context.

In my case, I was bind mounting /dev, /proc, /run, and /sys into my target directory prior to running debootstrap. There may have also been other pre-existing files inside the target directory.

I switched to running debootstrap on an empty directory. debootstrap then ran successfully.

[xiao-k233]

However, there is a 4GB limit to install using the img image. My sd card is not recognized by the system after formatting to ext4 format, what should I do?

[Sepero]

However, there is a 4GB limit to install using the img image. My sd card is not recognized by the system after formatting to ext4 format, what should I do?

You may be able to get a larger img size if you format your sdcard as internal storage

[AzeAstro]

FINALLY! I FOUND A WORKING ANSWER TO IT! The answer is setting installation path ${ENV_DIR}/rootfs/linux. Reference https://github.com/meefik/linuxdeploy/issues/832#issuecomment-320638140

[ScottRFrost]

As of time of this post, in Linux Deploy version 2.6.0-259 this bug still exists, and the path as described by @AzeAstro still fixes it. The default for directory should probably be changed to that.

For what it's worth, it also seems a decent amount faster than using the .img image file.

[mortissiamax]

More #2560 in package.and.a.antivirus.Le 31 mars 2022 21:13, "Scott R. Frost" @.***> a écrit : As of time of this post, in Linux Deploy version 2.6.0-259 this bug still exists, and the path as described by @AzeAstro still fixes it. The default for directory should probably be changed to that. For what it's worth, it also seems a decent amount faster than using the .img image file.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

[mortissiamax]

Dcmmmooooooomd chmod dcmmod Fonction chwmod data/ret/.fr.meefik/linux deploy

[mortissiamax]

More #2560 in package.and.a.antivirus.Le 31 mars 2022 21:13, "Scott R. Frost" @.***> a écrit : As of time of this post, in Linux Deploy version 2.6.0-259 this bug still exists, and the path as described by @AzeAstro still fixes it. The default for directory should probably be changed to that. For what it's worth, it also seems a decent amount faster than using the .img image file.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

**@Sepero unrecheable **no root

[mortissiamax]

FINALLY! I FOUND A WORKING ANSWER TO IT! The answer is setting installation path ${ENV_DIR}/rootfs/linux. Reference https://github.com/meefik/linuxdeploy/issues/832#issuecomment-320638140

<Liste lnux [envieDir].>

[mortissiamax]

However, there is a 4GB limit to install using the img image. My sd card is not recognized by the system after formatting to ext4 format, what should I do?

You may be able to get a larger img size if you format your sdcard as internal storage

Dowload magisk apk in android root carte sd ram 4g android root android.as internal storage

[Ritterbrater]

I stumbled over the message of the issue the second time now. First I thought, busybox is not installed properly.

I think I found the root of evil but it's probably not fixable: When choosing installation type: directory the installation path is: ${EXTERNAL_STORAGE}/linux

${EXTERNAL_STORAGE} expands to /storage/emulated/0/... All files and folders inside this path belong to group "everybody" (at least in my case of LOS 20, Android 13, Begonia). This corresponding group is 9997. This group cannot be changed. The even bigger issue might be: It's not possible to change any bits via chmod. So, no executable bit. When changing the installation path to ${ENV_DIR}/rootfs/linux as @AzeAstro linked to another post, everything works fine. Maybe because it is outside of the emulated storage (possibly mortissiamax tried to say this).