Fix -L flag for certain ARM64 distributions (#281) - #386
Open
zavocc wants to merge 1 commit into
Open
Conversation
…which dpkg uses since Ubuntu trusty era causing dpkg to fail until zesty
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It turns out the reason
dpkgkeeps failing or outputting symbolic size changes warnings or errors could be dpkg arm64 callsnewfstatat/fstatat64instead oflstat(2)(or could be glibc arm64's implementation) which fix_symlink_size extension only hookedlstat/lstatat64Note that I actually had this draft several months ago and had tested on Debian13 installation and Ubuntu 16.04 ARM64, so far I've never seen any errors or warnings dpkg complains symlink size changes as I use this patch. I only didn't open pull request since testing is needed as I only tested this on my device.
To test, run
apt update && apt upgradeon the target distribution with out-of-date packages before and after using this patchThis should hopefully fix #281