how to handle dangling symlinks while makepkg
#3685
-
On running makepkg -CLf for the PKGBUILD file (took from arch) for kakoune, following error is shown: $ makepkg -CLf
...
==> Extracting sources...
-> Extracting kakoune-2022.10.31.tar.bz2 with bsdtar
kakoune-2022.10.31/CHANGELOG: Can't create 'kakoune-2022.10.31/CHANGELOG': No such file or directory
kakoune-2022.10.31/libexec/kak/kak: Can't create 'kakoune-2022.10.31/libexec/kak/kak': No such file or directory
bsdtar: Error exit delayed from previous errors.
==> ERROR: Failed to extract kakoune-2022.10.31.tar.bz2
Aborting...Looking at
|
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 19 replies
-
|
Does your user have required privileges during the run?
|
Beta Was this translation helpful? Give feedback.
-
I am surprised. Do you have some examples of false positives for each way? |
Beta Was this translation helpful? Give feedback.
-
yeah, i have already documented these at least for the refer the table given here: #3685 (reply in thread) the 2nd row (red crossed arrow) - for the file of and shown further down at #3685 (reply in thread) is the output to these files from powershell's command - notice that the target column contains |
Beta Was this translation helpful? Give feedback.
-
|
You essentially flooded this thread, and I am having difficulty on how exactly could one reproduce the results. Is running With File Explorer shows no such item on the FS too. |
Beta Was this translation helpful? Give feedback.
-
sorry for that, yes, i haven't yet found a way to properly record the exploratory data.... i was looking for "hiding" my no longer relevant comments (and also marking the unrelevant threads to be collapsed by default), but that feature is not available in discussions yet on github anyhow, these are the versions i am having: $ uname -srv
MSYS_NT-10.0-19042 3.4.6.x86_64 2023-02-15 18:03 UTC
$ tar --version
bsdtar 3.5.2 - libarchive 3.5.2 zlib/1.2.5.f-ipp
$ bsdtar --version
bsdtar 3.6.2 - libarchive 3.6.2 zlib/1.2.13 liblzma/5.4.0 bz2lib/1.0.8 liblz4/1.9.4 libzstd/1.5.2i will try to think of some way to make it clear for you. but don't hold your breath, it may take long... maybe some weeks at minimum |
Beta Was this translation helpful? Give feedback.
-
|
In general I am OK with this because it's your thread. But I am still interested in why our results differs both:
OK, my next step will be to update my MSYS2 installation: |
Beta Was this translation helpful? Give feedback.
-
|
Alternatively, you can extract the tar file twice. For example, noextract=("foo.tar.xz")
prepare() {
tar -xf foo.tar.xz || tar -xf foo.tar.xz
} |
Beta Was this translation helpful? Give feedback.
-
|
shall i put noextract (array) between the resulting will become:
also, does the order even matter functionally? |
Beta Was this translation helpful? Give feedback.
-
No, the order does not matter. Though I generally follow the order. You can find some guidelines
|
Beta Was this translation helpful? Give feedback.
-
thanks, i just tried this now (in the admin/nativestrict environment), |
Beta Was this translation helpful? Give feedback.
-
|
i resolved to doing this: noextract=("kakoune-2022.10.31.tar.bz2")
prepare() {
cd $srcdir/
tar -xf kakoune-2022.10.31.tar.bz2
touch kakoune-2022.10.31/src/kak
tar -xf kakoune-2022.10.31.tar.bz2
} |
Beta Was this translation helpful? Give feedback.
-
|
ohkay, the
just noting for myself, figure out how to:
==> Extracting sources...
-> Extracting kakoune-2022.10.31.tar.bz2 with bsdtar
$ file CHANGELOG libexec/kak/kak
CHANGELOG: symbolic link to doc/pages/changelog.asciidoc
libexec/kak/kak: broken symbolic link to ../../src/kak
$ stat CHANGELOG libexec/kak/kakone surprising 🤔 thing is that,
|
Beta Was this translation helpful? Give feedback.
-
|
This difference is apparent on looking at the "Properties" panel of these files TODO: will add screenshots shortly For viewing the properties in command line, after quite research, i found the following syntax for the Get-Item -Path <string[]> | Format-List -Property <Object[]>
# aliased, & shortcut form
gi <string[]> | fl <Object[]>where Derivation journey, bit-by-bitadding the calculated property : thus results in: gi changelog,.\libexec\kak\kak | fl Name,Mode,Attributes,LinkType,Target,@{label="Parent";expression={$_.Directory.BaseName}}doing some restructuring, required output format for table is: Attributes, Mode, Name, LinkType, Target, @{label="Parent";expression={$_.Directory.BaseName}... putting some ".\CHANGELOG",".\libexec\kak\kak" | ForEach {gi $_} | ft Attributes, Mode, Name, LinkType, Target, @{label="Parent";expression={$_.Directory.BaseName}}Add some validity checking, and whitespacing for readability: ".\CHANGELOG",".\libexec\kak\kak" | ForEach {if (!(Test-Path $_)) {"`r`n"}; gi $_} | ft Attributes, Mode, Name, LinkType, Target, @{label="Parent";expression={$_.Directory.BaseName}Add somth on the likes of brace expansion: "kakoune-2022.10.31"| % {} {"$_-native"} {"$_-nativestrict"} {} | % {} {"$_-tar"} {"$_-bsdtar"} {} | % {} {"$_\CHANGELOG"} {"$_\libexec\kak\kak"} {} | ForEach {if (!(Test-Path $_)) {"`r`n"}; gi $_} | ft Attributes, Mode, Name, LinkType, Target, @{label="Parent";expression={$_.Directory.BaseName}}Clean-up the directories to show correct relative paths: "kakoune-2022.10.31"| % {} {"$_-native"} {"$_-nativestrict"} {} | % {} {"$_-tar"} {"$_-bsdtar"} {} | % {} {"$_\CHANGELOG"} {"$_\libexec\kak\kak"} {} | ForEach {if (!(Test-Path $_)) {"`r`n"}; gi $_} | ft Attributes, Mode, Name, LinkType, Target, @{label="Parent";expression={Resolve-Path $_.Directory -Relative}}The per-directory usage version: "CHANGELOG", ".\libexec\kak\kak" | ForEach {if (!(Test-Path $_)) {"`r`n"}; gi $_} | ft Attributes, Mode, Name, LinkType, Target |
Beta Was this translation helpful? Give feedback.
-
|
Done in the comment below Console logs for the Powershell commandlets
# Empty - hence the "Red Ptr to Cross" in doublecmd
PS \> cd ..\kakoune-2022.10.31-native-bsdtar\
PS \> gi changelog,.\libexec\kak\kak | fl LinkType,Target
LinkType :
Target : {}
LinkType :
Target : {}
PS \> cd ..\kakoune-2022.10.31-native-tar\
PS \> gi changelog,.\libexec\kak\kak | fl LinkType,Target
LinkType :
Target : {}
LinkType :
Target : {}
# Only the changelog is pointing somewhere, hence the green pointer in doublecmd
PS \> cd ..\kakoune-2022.10.31-nativestrict-tar\
PS \> gi changelog,.\libexec\kak\kak | fl LinkType,Target
LinkType : SymbolicLink
Target : {doc\pages\changelog.asciidoc}
gi : Cannot find path 'D:\15_devt\abs\kakoune\kakoune-2022.10.31-nativestrict-tar\libexec\kak\kak' because it does not exist.
At line:1 char:1
+ gi changelog,.\libexec\kak\kak | fl LinkType,Target
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (D:\15_devt\abs\...libexec\kak\kak:String) [Get-Item], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand
PS \> cd ..\kakoune-2022.10.31-nativestrict-bsdtar\
PS \> gi changelog,.\libexec\kak\kak | fl LinkType,Target
gi : Cannot find path 'D:\15_devt\abs\kakoune\kakoune-2022.10.31-nativestrict-bsdtar\changelog' because it does not exist.
At line:1 char:1
+ gi changelog,.\libexec\kak\kak | fl LinkType,Target
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (D:\15_devt\abs\...sdtar\changelog:String) [Get-Item], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand
gi : Cannot find path 'D:\15_devt\abs\kakoune\kakoune-2022.10.31-nativestrict-bsdtar\libexec\kak\kak' because it does not exist.
At line:1 char:1
+ gi changelog,.\libexec\kak\kak | fl LinkType,Target
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (D:\15_devt\abs\...libexec\kak\kak:String) [Get-Item], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand |
Beta Was this translation helpful? Give feedback.
-
|
i just tested with msys launcher with admin privileges, and while the |
Beta Was this translation helpful? Give feedback.
-
|
It's kinda impressive that in 8 hours, i went from having never used powershell before (never as in just used in 2-3 distant sets of 5-6 minutes) to writing this whole thing on my own reading documentation. waow. PS kakoune> "kakoune-2022.10.31"| % {} {"$_-native"} {"$_-nativestrict"} {} | % {} {"$_-tar"} {"$_-bsdtar"} {} | % {} {"$_\CHANGELOG"} {"$_\lib
exec\kak\kak"} {} | ForEach {if (!(Test-Path $_)) {"`r`n"}; gi $_} | ft Attributes, Mode, Name, LinkType, Target, @{label="Parent";expression={Resolve-Path $_
.Directory -Relative}}
Attributes Mode Name LinkType Target Parent
---------- ---- ---- -------- ------ ------
Archive, ReparsePoint -a---l CHANGELOG {} .\kakoune-2022.10.31-native-tar
Archive, ReparsePoint -a---l kak {} .\kakoune-2022.10.31-native-tar\libexec\kak
Archive, ReparsePoint -a---l CHANGELOG {} .\kakoune-2022.10.31-native-bsdtar
Archive, ReparsePoint -a---l kak {} .\kakoune-2022.10.31-native-bsdtar\libexec\kak
Archive, ReparsePoint -a---l CHANGELOG SymbolicLink {doc\pages\changelog.asciidoc} .\kakoune-2022.10.31-nativestrict-tar
gi : Cannot find path 'kakoune\kakoune-2022.10.31-nativestrict-tar\libexec\kak\kak' because it does not exist.
At line:1 char:192
+ ... \kak\kak"} {} | ForEach {if (!(Test-Path $_)) {"`r`n"}; gi $_} | ft A ...
+ ~~~~~
+ CategoryInfo : ObjectNotFound: (...libexec\kak\kak:String) [Get-Item], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand
gi : Cannot find path 'kakoune\kakoune-2022.10.31-nativestrict-bsdtar\CHANGELOG' because it does not exist.
At line:1 char:192
+ ... \kak\kak"} {} | ForEach {if (!(Test-Path $_)) {"`r`n"}; gi $_} | ft A ...
+ ~~~~~
+ CategoryInfo : ObjectNotFound: (...sdtar\CHANGELOG:String) [Get-Item], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand
gi : Cannot find path 'kakoune\kakoune-2022.10.31-nativestrict-bsdtar\libexec\kak\kak' because it does not exist.
At line:1 char:192
+ ... \kak\kak"} {} | ForEach {if (!(Test-Path $_)) {"`r`n"}; gi $_} | ft A ...
+ ~~~~~
+ CategoryInfo : ObjectNotFound: (...libexec\kak\kak:String) [Get-Item], ItemNotFoundException
+ FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand |
Beta Was this translation helpful? Give feedback.
-
|
so, i tried a hack: creating a dummy # pwd=kakoune\kakoune-2022.10.31
cd src
touch kak
cd ..
cd libexec/kak
powershellcd .\libexec\kak\; New-Item -ItemType SymbolicLink -Path ./kak -Target ../../src/kak; cd ../../;
"CHANGELOG", ".\libexec\kak\kak" | ForEach {if (!(Test-Path $_)) {"`r`n"}; gi $_} | ft Attributes, Mode, Name, LinkType, TargetIt required admin privilegesNew-Item : Administrator privilege required for this operation.
At line:1 char:1
+ New-Item -ItemType SymbolicLink -Path ./kak -Target ../../src/kak -Fo ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : PermissionDenied: (D:\15_devt\abs\...2.10.31\s
rc\kak:String) [New-Item], UnauthorizedAccessException
+ FullyQualifiedErrorId : NewItemSymbolicLinkElevationRequired,Microsoft
.PowerShell.Commands.NewItemCommandso, i opened the msys launcher elevated. but still, the check above showed that the symlink created is absolute.... huh :) |
Beta Was this translation helpful? Give feedback.
Alternatively, you can extract the tar file twice. For example,