When running pacman -Qkk after the upgrade to 4.1.0, I am now getting "no mtree file" for all packages on my system. These errors did not occur prior to the upgrade, and I upgraded no other packages. Does this indicate breakage? How should I fix this?
Last edited by cdown (2013-04-05 02:05:35)
The only way to fix this is to rebuild all packages using makepkg from pacman-4.1....
So this is not breakage that I can fix on my end, then?
I looked at the libalpm source for information about mtrees, it looks like they are used to provide package integrity validation, but it's possible I'm wrong since I only read a small part of the code on mtrees. I'd appreciate information about what they are and what issues lacking them could cause.
Issues resulting from lack of mtree files include:
1) errors when running pacman -Qkk
So they serve no other practical purpose in daily use? Am I right in reading from the libalpm source that they only provide integrity validation?
Yes - it is a new feature of pacman-4.1 which requires a file in the package that is added but makepkg in pacman-4.1.