It looks like Portage now stores unicode paths correctly in its metadata as opposed to what it used to be. We need to make sure that we parse those "CONTENTS" file and content metadata in general using the correct encoding. This will allow us to store and retrieve such metadata from the sqlite3 database correctly and also match the stored paths with the filesystem paths exactly. This commit may need a bit more real-life testing. Backward compat wrt old Entropy and Portage tbz2 files should be as expected. Unit tests attached.
5.0 KiB
5.0 KiB