Summary: | sys-apps/portage-3.0.38.1-r1 creates non compliant Manifest files with --digest option | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Pacho Ramos <pacho> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pacho Ramos
![]() In general it's best to use dev-util/pkgdev for generating manifests; I wasn't even aware `emerge` was capable of doing it. Given there's better tooling for it, maybe we should just remove `emerge --digest`? The manpage even still references repoman as being the proper way to generate Manifests: --digest Prevent corruption from being noticed. The `repoman manifest` command is the preferred way to generate manifests and it is capable of doing an entire repository or category at once (see repoman(1)). I guess it is probably doing the right thing as it seems also pkgdev creates the complete Manifest when run out of the git tree. I guess I will need to get used to regenerate the Manifest two times: first time to allow it to be merged and used (as I usually get this when I start working on a new package), a second time when going to commit the package (instead of simply copying the files I was using during the testing) I am unable to reproduce the issue. emerge --digest creates a thin manifest here. Are you running emerge --digest in a repo that does not have the "thin-manifests" option set in metadata/layout.conf? If you are doing development work in a separate repository, you need to set up that repository correctly. OK, thanks for the tip! |