Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot build heroku-cli package with pikaur and yay #22

Closed
xd003 opened this issue Aug 26, 2020 · 103 comments
Closed

cannot build heroku-cli package with pikaur and yay #22

xd003 opened this issue Aug 26, 2020 · 103 comments
Labels
enhancement New feature or request no-issue-activity

Comments

@xd003
Copy link

xd003 commented Aug 26, 2020

I was trying to install this heroku-cli package from yay - https://aur.archlinux.org/packages/heroku-cli

yay -S heroku-cli

During the installation at the end , i got the following error and the yay installer aborted

chown: changing ownership of '/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/node_modules/treeify/examples/eukaryotes.js': Operation not permitted          
chown: changing ownership of '/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/node_modules/treeify/examples/fs_tree.js': Operation not permitted             
chown: changing ownership of '/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/node_modules/treeify/examples': Operation not permitted                       
chown: changing ownership of '/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/node_modules/treeify/treeify.js': Operation not permitted                      
chown: changing ownership of '/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/node_modules/treeify/test/tree-test.js': Operation not permitted 

NOTE - There were many more such lines ( in 100's tbh , i am not posting all but this should be enough

==> ERROR: A failure occurred in package().                       Aborting...

yay version -10.0.4-1

I tried installing same package on my laptop running on arch linux system but i didn't got any error , its very less likely that this is actually a upstream or heroku-cli package issue

@xd003 xd003 changed the title Unable to install heroku-cli from yay Unable to install heroku-cli package from yay Aug 26, 2020
@SDRausty
Copy link
Contributor

I tried installing same package on my laptop running on arch linux system but i didn't got any error

@xd003 I tried both builds of heroku-cli on my smartphone with yay. Both builds were unsuccessful, and none of them had errors related to permissions.

Since your builds are successful on the laptop, but not on a smartphone, I suggest reaching out to Arch Linux groups to find out what the underlying cause of this difference in builds might be. How do you like the way yay cmatrix builds on a smartphone?

@SDRausty
Copy link
Contributor

@xd003 even though you got a permission denied error, does the final product heroku-cli work? The reason I am asking you this question is after running into a couple of programs built with yay and this last one built with the command pikaur cmatrix came up with the same error that you got, permission denied. However the final result, the product works at expected!

See if you can reproduce this with one of The Matrix screensaver programs. I tried tmatrix-git and got a permission denied error, and as I mentioned the program works as expected. This is quite surprising, isn't it?

@xd003
Copy link
Author

xd003 commented Aug 27, 2020

@SDRausty any heroku command doesn't work , it says zsh : command not found : heroku . In fact pacman -Q | grep heroku doesn't return anything implying it hasn't got installed at all

On another note , I didn't got any permission denied errors while installing tmatrix-git. It got installed well - ``tmatrix --version``` rightly returned the latest version

Regarding the heroku thing , lemme discuss it with the arch linux chat group in telegram , if it gets fixed by doing something , i will definitely suggest it here

@SDRausty
Copy link
Contributor

the final result

The way permissions are configured has been revised; Hopefully this change will have a positive effect on our devices and heroku-cli will build for you as expected. It is still not building as you can see on my smartphone:

[user11:55~]$ yay -S heroku-cli
⋮
==> Entering fakeroot environment...
==> Starting package()...
/home/user/.cache/yay/heroku-cli/PKGBUILD: line 23: 30501 Illegal instruction     npm install -g --user root --prefix "$pkgdir/usr" --cache "$srcdir/npm-cache" heroku-$pkgver.tgz
==> ERROR: A failure occurred in package().
    Aborting...
error making: heroku-cli
[user11:59~]$ npm
Illegal instruction
[user11:59~]$ l
total 100
drwxrwxrwx  6 user user 4096 Aug 28 11:55 .
drwxr-xr-x 10 user user 4096 Aug 28 11:54 ..
-rw-------  1 user user   73 Aug 28 11:47 .bash_history
-rw-------  1 user user  104 Aug 28 10:52 .bash_logout
-rw-------  1 user user  796 Aug 28 11:31 .bash_profile
-rw-------  1 user user  976 Aug 28 11:31 .bashrc
drwx------  2 user user 4096 Aug 28 11:47 bin
drwx------  4 user user 4096 Aug 28 11:55 .cache
drwxr-xr-x  3 user user 4096 Aug 28 11:55 .config
drwx------  3 user user 4096 Aug 28 10:52 .gnupg
-rw-------  1 user user   20 Aug 28 10:52 .inputrc
-rw-------  1 user user    0 Aug 28 10:52 .profile
-rw-------  1 user user 1159 Aug 28 11:47 .viminfo

It appears that npm does not work well for some reason on arm7 Android. @xd003 are you also using arm7 architecture too?

@SDRausty
Copy link
Contributor

SDRausty commented Aug 29, 2020

PermissionError: [Errno 13] Permission denied: '/home/user/.local/share/pikaur/aur_repos/ncmatrix/last_installed.txt' when building pikaur cmatrix choice 2) aur/ncmatrix 1.0-1 [installed] (15, 0.00). The error stsrts at:

Traceback (most recent call last):
  File "/usr/bin/pikaur", line 9, in <module>
    main()
  File "/usr/lib/python3.8/site-packages/pikaur/main.py", line 437, in main
    cli_entry_point()

The directory structure seems okay:

[user19:26~]$ l
total 64
drwxrwxrwx 9 user user 4096 Aug 29 19:10 .
drwxr-xr-x 4 user user 4096 Aug 28 23:03 ..
-rw------- 1 user user   38 Aug 29 19:22 .bash_history
-rw------- 1 user user  104 Aug 28 23:03 .bash_logout
-rw------- 1 user user  796 Aug 29 19:07 .bash_profile
-rw------- 1 user user  976 Aug 29 19:07 .bashrc
drwx------ 2 user user 4096 Aug 28 23:03 bin
drwxr-xr-x 5 user user 4096 Aug 29 19:10 .cache
drwxr-xr-x 3 user user 4096 Aug 29 19:10 .config
-rw-r--r-- 1 user user  679 Aug 29 00:14 diff.makepkg.zip
drwxr-xr-x 5 user user 4096 Aug 29 18:49 fakeroot-tcp
drwx------ 3 user user 4096 Aug 28 23:03 .gnupg
-rw-r--r-- 1 user user    0 Aug 29 00:03 .hushlogin
-rw-r--r-- 1 user user    0 Aug 29 00:03 .hushlogout
-rw------- 1 user user   20 Aug 28 23:03 .inputrc
drwxr-xr-x 3 user user 4096 Aug 29 19:10 .local
-rw-rw---- 1 user user 1289 Jul 19 06:14 makepkg.diff
-rw------- 1 user user    0 Aug 28 23:03 .profile
drwxr-xr-x 5 user user 4096 Aug 29 19:01 yay

The program ncmatrix built as expected. Which by now is unsurprising behavior. Did you know that python3 is historically less stable than python2 in Termux? And how does your permission denied error begin? Does it also begin with Python3? @TermuxArch/termuxarch

@SDRausty

This comment has been minimized.

@guozhenduo
Copy link

guozhenduo commented Aug 30, 2020 via email

@SDRausty
Copy link
Contributor

These two screenshots show what I am finding when pursuing this issue of building with pikaur. This screenshot shows the program failed to build when python3 was envoked. Yet did build ncmatrix, but the build process did not go quite as expected for there was a permission flag:
Screenshot_20200829.png

This screenshot shows the program ncmatrix that built on an armv7l Android 10 smartphone in action:
Screenshot_20200830.png

The machine used was armv7l Android 10 smartphone. The command run as user was makeyay && yay pikaur && pikaur cmatrix. What command preceded chown: changing ownership of '/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/node_modules/treeify/examples/eukaryotes.js': Operation not permitted when the screen showed you a similar permission denied error @xd003?

@xd003
Copy link
Author

xd003 commented Aug 30, 2020

@SDRausty
Firstly I am Sorry for replying a bit late , the internet here was down since past 2 days ,now coming back to the topic

  1. Since you had asked - i am running termux on a arm64-v8 device with Android 7 . ( uname -m in termux returns aarch64)

  2. The whole output was pretty large , hence i had pasted only few lines from it although i understand for proper debugging whole output is must. So here's the whole output from start to end - https://gist.githubusercontent.com/xd003/ecb331990a55bd609f5bd72afe4ac60e/raw/2eb24364cefe229667b53646deeaa763abb31864/yay-output.txt
    Hopefully it will be helpful

  3. Also you had suspected if npm not working well on your armv7 device might be a armv7 or rootfs proot restriction , i personally don't believe so . Reason being i have used Ubuntu rootfs proot in past and have successfully installed heroku-cli without any issues so most likely its something to do with termuxarch itself

  4. Lastly i am also trying to get some suggestions on this issue from my end. i haven't had much success in the arch linux chat group , i also did posted this issue in Stack Overflow , waiting for suggestions . I will keep you updated if there's any clue

@SDRausty
Copy link
Contributor

  1. Since you had asked - i am running termux on a arm64-v8 device with Android 7 . ( uname -m in termux returns aarch64)

This explains the difference in the errors that we are encountering as we are using different architectures and different versions of Android.

  1. The whole output was pretty large , hence i had pasted only few lines from it although i understand for proper debugging whole output is must. So here's the whole output from start to end - https://gist.githubusercontent.com/xd003/ecb331990a55bd609f5bd72afe4ac60e/raw/2eb24364cefe229667b53646deeaa763abb31864/yay-output.txt
    Hopefully it will be helpful

What was the preceding error?

  1. Also you had suspected if npm not working well on your armv7 device might be a armv7 or rootfs proot restriction , i personally don't believe so . Reason being i have used Ubuntu rootfs proot in past and have successfully installed heroku-cli without any issues so most likely its something to do with termuxarch itself

How do you install heroku-cli? Did you build it?

  1. Lastly i am also trying to get some suggestions on this issue from my end. i haven't had much success in the arch linux chat group , i also did posted this issue in Stack Overflow , waiting for suggestions . I will keep you updated if there's any clue

I will appreciate it very much. Hopefully we can find out what is causing this issue.

@SDRausty
Copy link
Contributor

There is also the option of building with pikaur after using yay pikaur. From the literature that I have read about pikaur, it asks more questions than yay. Using pikaur might help in getting a successful result.

@SDRausty
Copy link
Contributor

SDRausty commented Aug 30, 2020

@xd003 I am still trying to grasp this issue, and I just noticed https://github.com/heroku/cli/issues. So my next suggestion is opening an issue right there to get answers. This might find a solution the fastest 🚀

@SDRausty
Copy link
Contributor

SDRausty commented Aug 30, 2020

The issue at npm This is an error with npm itself. Please report this error... #19239 has not seem to made much progress. This issue has changed a little bit in the last 3 years; Adding information about what is happening in the Android environment might be very helpful @xd003...

EDIT It appears this repository was archived.

@SDRausty
Copy link
Contributor

SDRausty commented Aug 30, 2020

[user19:43~]$ pikaur heroku-cli
==> Entering fakeroot environment...
==> Starting package()...
/home/user/.cache/pikaur/build/heroku-cli/PKGBUILD: line 23: 24758 Illegal instruction     
npm install -g --user root --prefix "$pkgdir/usr" --cache "$srcdir/npm-cache" heroku-$pkgver.tgz
==> ERROR: A failure occurred in package().
    Aborting...

@xd003
Copy link
Author

xd003 commented Aug 31, 2020

@SDRausty

==> Validating source files with sha256sums...
    heroku-7.42.8.tgz ... Passed
==> Validating source files with sha512sums...
    heroku-7.42.8.tgz ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
==> Sources are ready.
==> Making package: heroku-cli 7.42.8-1 (Sun 30 Aug 2020 08:49:53 AM UTC)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Removing existing $pkgdir/ directory...
==> Entering fakeroot environment...
==> Starting package()...
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/bin/heroku -> /home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/bin/run
+ heroku@7.42.8
added 733 packages from 310 contributors in 206.34s

These are are lines exactly prior to the start of the chown permission error

In Ubuntu ,i had installed it by using the standalone script method mentioned below . This method supposedly is universal to all platforms because it uses tarball and is equivalent to building heroku-cli manually

i forgot to mention earlier but i had also tried this this standalone script in TermuxArch from heroku website - curl https://cli-assets.heroku.com/install.sh | sh ,just edit the line 37 according the uname -m output from your device . This method too was unsuccessful and it ended up with some error while extracting the .tar.gz file
here is the full output - https://gist.githubusercontent.com/xd003/41606ebb63d1d195accdc5303851f985/raw/94921e042986e0ac4454ad3999fd3e1e0b5115d4/heroku-script.txt

i wlll definitely raise a issue in github.com/heroku/cli , thanks for bringing it to my attention

Lastly i also tried pikaur as you had suggested , but it seems returning the same errors like yay . Here is the full output - https://gist.githubusercontent.com/xd003/e66067192d4f4106e17c19e6c7255bc0/raw/9b325a82722987aa26099dce78a775dd0ff1cea2/pikaur-output.txt

@SDRausty
Copy link
Contributor

SDRausty commented Aug 31, 2020

These lines we were looking for:

npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/bin/heroku -> /home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/bin/run

These are are lines exactly prior to the start of the chown permission error

@xd003 thank you for your insight regarding the lines exactly prior; can you summarize the last two outputs of data in the same way as the first one was summerized please?

@SDRausty
Copy link
Contributor

issue has changed a little bit in the last 3 years

@xd003
Copy link
Author

xd003 commented Aug 31, 2020

@SDRausty

  1. Regarding the standalone script method , there wasn't anything special .As you can see the script downloaded the file then this error got spammed way too times for different heroku cli files ..
0:00:21  0:00:11  0:00:10  767k
 54 16.1M   54 9006k    0     0   754k      0  0:00:21  0:00:11  0:00:10  742ktar: heroku/bin: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/lib/hooks/prerun: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/lib/hooks/update: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/lib/hooks/init: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/lib/hooks: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/lib: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/node_modules/safe-buffer: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/node_modules/figures: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/node_modules/ansi-styles: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/node_modules/cross-spawn/lib/util: Cannot change mode to rwxr-xr-x: Invalid argument
tar: heroku/node_modules/cross-spawn/lib: Cannot change mode to rwxr-xr-x: Invalid argument
...
...
... x 100's of lines of same format for different files ie.
**tar: some/file: Cannot change mode to rwxr-xr-x: Invalid argument**
  1. Regarding the heroku-cli installation with pikaur. Here are the lines exactly prior to the start of the error
:: Starting the build:
==> Making package: heroku-cli 7.42.8-1 (Mon 31 Aug 2020 02:59:52 AM UTC)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading heroku-7.42.8.tgz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 14937  100 14937    0     0  54514      0 --:--:-- --:--:-- --:--:-- 54714
==> Validating source files with sha256sums...
    heroku-7.42.8.tgz ... Passed
==> Validating source files with sha512sums...
    heroku-7.42.8.tgz ... Passed
==> Extracting sources...
==> Entering fakeroot environment...
==> Starting package()...
npm WARN deprecated mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
/home/xd003/.cache/pikaur/build/heroku-cli/pkg/heroku-cli/usr/bin/heroku -> /home/xd003/.cache/pikaur/build/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/bin/run
+ heroku@7.42.8
added 733 packages from 310 contributors in 277.133s
chown: changing ownership of '/home/xd003/.cache/pikaur/build/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/bin/run': Operation not permitted
chown: changing ownership of '/home/xd003/.cache/pikaur/build/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/bin/run.cmd': Operation not permitted
...
...
...
x 100's of lines of same format ie
**chown : changing permission of some/file: Operation not permitted**

Hopefully this will be helpful

@SDRausty
Copy link
Contributor

Information from https://github.com/npm/npm:

https://github.com/npm/npm#weve-moved

This short search gave three results at the new npm project:

https://github.com/npm/cli/issues?q=is%3Aissue+heroku-cli

$ pci npm

This command installs npm in our environment, which is what pikaur and yay do anyway; npm result:

[user06:05~]$ npm
Illegal instruction

@SDRausty
Copy link
Contributor

SDRausty commented Aug 31, 2020

Permissions can also be at fault here:

tried installing same package on my laptop running on arch linux system but i didn't get any error

$ find ~/arch/home/user/ -type d -exec chmod 777 {} \;

Is there any positive effect if you change the permission scheme of the user directory @xd003?

@SDRausty
Copy link
Contributor

SDRausty commented Aug 31, 2020

Taking this issue one step further, especially for users just testing the installed system for the purpose of just testing it:

find ~/arch/ -type d -exec chmod 777 {} \;

How does this command affect the behavior of the in installed system?

@SDRausty
Copy link
Contributor

SDRausty commented Aug 31, 2020

After thorough testing (dozens), this part of commit 5fc7da0#diff-7d122b07f71ef4ad6b416eaa0eb882e5R435 rewrites the creation of permissions in Arch Linux in Termux PRoot. You probably will want to reinstall the entire system for these changes to fully take place as it affects the entire system. However, if you simply wish to continue with refreshing the system (not really recommended if you are compiling) tweakingumask in file /etc/profile is advised. The system can be refreshed with command setupTermuxArch re:

[re [customdir]] Refresh the Arch Linux in Termux PRoot scripts created by TermuxArch. Useful for refreshing the root user's home directory and user home directories and the TermuxArch generated scripts to their newest version.

I have spent much time analyzing this and similar issues, especially when it regards permissions. As you might imagine a system... A system that is nested in another system, that is nested in still another system twice! I am referring to Android > Termux > PRoot nesting along with SELinux fusion makes this issue an amazingly interesting topic. Thank you for opening this issue @xd003.

$ yay heroku-cli
⋮
2 aur/heroku-cli-nightly 6.14.20.737bba7-1 (+2 0.00) (Orphaned) (Out-of-date: 2020-07-15)                                                                     
a tool for creating and managing Heroku apps from the command line        
1 aur/heroku-cli 7.42.8-1 (+55 3.37) (Out-of-date: 2020-08-30)                    
a tool for creating and managing Heroku apps from the command line
⋮
==> Starting package()...
/home/u/.cache/yay/heroku-cli/PKGBUILD: line 23: 25965 Illegal instruction     npm install -g --user root --prefix "$pkgdir/usr" --cache "$srcdir/npm-cache" heroku-$pkgver.tgz
==> ERROR: A failure occurred in package().
    Aborting...
error making: heroku-cli
$ npm
Illegal instruction

It did not magically build as far as I can tell either. The command pcss heroku-cli produced nothing. So it is not there. It has not installed.

chown: changing ownership of '/home/xd003/.cache/yay/heroku-cli/pkg/heroku-cli/usr/lib/node_modules/heroku/node_modules/treeify/examples/eukaryotes.js': Operation not permitted
chown:

Since we are using very different machines, even though they probably look very much alike, your error might be resolved. Does the command npm work correctly in aarch64? Can you reinstall the system to see how heroku-cli builds in aarch64 please?

@SDRausty
Copy link
Contributor

SDRausty commented Nov 10, 2020

Sure. I could also download newer Tarbal.

Thank you for sharing; It appears upstream is gone! I'm not sure what to do to resolve this. I shared our success at Arch Linux on Reddit, and this share was locked and taken down, "Such gross and blatant clickbait on this sub ? Am I the only one to feel that this post should be moderated, at least as is ?"

Screenshot_20201110-090705
Screenshot_20201110-090723

Since it appears that upstream disappeared after I shared at Reddit and this share was locked and taken down, I mailed the maintainers of fakeroot-tcp at Arch Linux and am awaiting a reply. What is your opinion about this turn of events?

@SDRausty
Copy link
Contributor

  1. We are already building amazing creations on Android smartphones,
  2. Where is the source code for the package we are missing?
  3. My suggestion is to proceed with this quest similar to what command 'csystemctl' does in TermuxArch, which is to include the build tools we already are using anyway and to build 'fakeroot-tpc` from source into package on device to attempt to resolve this topic.

Do you agree with this proposed solution?

@SDRausty
Copy link
Contributor

SDRausty commented Dec 10, 2020

@xd003 have you heard the news regarding the death of our coder helper Harper? She was shot dead on 20201201 @1630. No water quality specialists are allowed to live in Flint, Michigan USA @present, only human set free water quality forgers!

Why was my water qualty specialist https://serviceanimals.github.io/Harper/ shot dead by Flint City Michigan USA police?

I asked the Flint City Mayor. They have not replied.

@SDRausty
Copy link
Contributor

I am managing to build two out of the four heroku aur Arch Linux packages of heroku available on my smartphone. Hours of attempts a couple of days ago have brought about unimpressive results:
[user22:17TermuxArch]$ heroku --help Illegal instruction

Referencing the news about our coder Harper updates...

@JanuszChmiel
Copy link

JanuszChmiel commented Dec 13, 2020 via email

@SDRausty
Copy link
Contributor

mailed the maintainers of fakeroot-tcp at Arch Linux and am awaiting a reply.

5 days agoDetails
The package fakeroot-tcp [1] was adopted by w0rty [2].

[1] https://aur.archlinux.org/pkgbase/fakeroot-tcp/
[2] https://aur.archlinux.org/account/w0rty/

@JanuszChmiel
Copy link

JanuszChmiel commented Dec 13, 2020 via email

@JanuszChmiel
Copy link

JanuszChmiel commented Dec 13, 2020 via email

@JanuszChmiel
Copy link

JanuszChmiel commented Dec 13, 2020 via email

@JanuszChmiel
Copy link

JanuszChmiel commented Dec 13, 2020 via email

@JanuszChmiel
Copy link

JanuszChmiel commented Dec 13, 2020 via email

@JanuszChmiel
Copy link

JanuszChmiel commented Dec 13, 2020 via email

@JanuszChmiel
Copy link

JanuszChmiel commented Dec 13, 2020 via email

@SDRausty
Copy link
Contributor

SDRausty commented Dec 16, 2020

Thank you for asking. Were service coder dog Harper about, the news probably would not be much different @present; All updates including Android updates seem be causing PRoot emulated fail.

@SDRausty SDRausty unpinned this issue Dec 20, 2020
@github-actions
Copy link

github-actions bot commented Mar 1, 2021

Stale issue message

@github-actions github-actions bot closed this as completed Mar 9, 2021
@SDRausty SDRausty added the enhancement New feature or request label Jul 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment