You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Android 6.0 on my Google Nexus 5X, the link(2) system call is disabled; it always fails with EACCES (link). dpkg requires the ability to hard link in order to make an atomic backup of the status file (function atomic_file_backup), and currently, packages cannot be installed because it cannot do so.
As a result, this package isn't very useful on Android 6.0. dpkg probably needs to be patched so that it can perform a copy when link(2) isn't available.
The text was updated successfully, but these errors were encountered:
On Android 6.0 on my Google Nexus 5X, the link(2) system call is disabled;
it always fails with EACCES (link) https://stackoverflow.com/questions/32365690/is-android-m-not-allowing-hard-links.
dpkg requires the ability to hard link in order to make an atomic backup of
the status file (function atomic_file_backup), and currently, packages
cannot be installed because it cannot do so.
As a result, this package isn't very useful on Android 6.0. dpkg probably
needs to be patched so that it can perform a copy when link(2) isn't
available.
—
Reply to this email directly or view it on GitHub #8.
On Android 6.0 on my Google Nexus 5X, the link(2) system call is disabled; it always fails with EACCES (link). dpkg requires the ability to hard link in order to make an atomic backup of the status file (function
atomic_file_backup
), and currently, packages cannot be installed because it cannot do so.As a result, this package isn't very useful on Android 6.0. dpkg probably needs to be patched so that it can perform a copy when link(2) isn't available.
The text was updated successfully, but these errors were encountered: