I’ve found the problem.
Because the aur repo is cloned at a usb disk that format as ntfs on Windows, after recent updates of Manjaro, when automounted, it show a strange path as /run/media/aaa/D:\/, I think this caused the problem. Anyway to solve this?
$ makepkg -g
==> Retrieving sources...
-> Found vscodium-bin.desktop
-> Found VSCodium-linux-x64-1.51.1.tar.gz
==> Generating checksums for source files...
sha256sums=('\65e6b053e6d8be61763801312ded64a82cf835d77a6eabe1b9d7eb9e87b2e49b')
sha256sums_x86_64=('\cb2ee41c1b1042d4ebfb5e644ec59ded3fe6ce77c15abcd67078fca52abec442')
package problem
==> Starting package()...
cp: cannot stat '/run/media/aaa/D:\/aur/vscodium-bin/src/!(vscodium-bin.desktop|vscodium-bin-1.51.1.tar.gz)': No such file or directory
==> ERROR: A failure occurred in package().
Aborting...
Seems the packager has not updated the checksum, you can workaround this by writing ('SKIP') instead of the checksum.
It is really a bad behavior to have a path like with /package\/path/ Please avoid this. Because in scripts \ before a character means normally it will be used as normal character. Therefore after / will after \ will be normal character and not a “path boundary”.
thunar uses the partition name for creatung a mountpoint. Therefore, if the partition is named D:\, then you should change that and remove \. D: should work fine.
Please, write the problems occuring calmly. If you just say things willy nilly nobody is going to be able to help you and you could also end up being flagged.
Now, If the problem is a language barrier feel free to write it down on google translate and explain there, with as much detail as possible, what is the problem you are having.
Okay So, Are you reporting a bug in thunar-volman ?
Okay, It could be just the procedure to automount a usb drive, It couldn’t even be a thunar-volman “bug”.
Do you have any proof that it is thunar-volman that controls the automounting ?
Whats odd is that thunar-volman has been this version since May in Arch and Manjaro-Unstable.
(and the package comes directly from Arch)
And I dont know of any other such reports …
I tried to turn off “Enable Volume Management” in thunar preference, but the usb disk still shows as “D:”, and after click, it is automounted as “/run/media/aaa/D:/”.
Who makes the path “/run/media/aaa/D:/”? I have a almost fresh installed Manjaro.
Let’s work together and we’ll reach a solution. Have you tried reformatting this usb ?
Try using another USB Drive, with another format, and another with a ntfs format
(If you don’t have other USB drives, use this one if you can format it, if you can’t don’t destroy your data just to test it)
So the problem isn’t ntfs. Ok that solved a lot of trouble.
Hm, did you mean this:
"The previous usb disk that has the problems with makepkg, is from a laptop and has installed windows on it, the partition table is very windows style: "?
If so then I have to ask if the drive is encrypted, probably not since you can mount manually.