Summary: | sys-apps/portage-2.1.12.2: repoman ci --echangelog y creates invalid manifests | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Kent Fredric (IRC: kent\n) (RETIRED) <kentnl> |
Component: | Repoman | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 472632 | ||
Attachments: |
output of emerge --info sys-apps/portage
linked github gists & overlay tree bundled |
Description
Kent Fredric (IRC: kent\n) (RETIRED)
2013-08-14 05:38:27 UTC
Created attachment 355940 [details]
linked github gists & overlay tree bundled
Just attaching these output lines as a tarball as a backup plan if the gists ever go down ( however unlikley it may be )
Repoman auto-writes the changelog, so you don't need to pass that option (In reply to Agostino Sarubbo from comment #2) > Repoman auto-writes the changelog, so you don't need to pass that option Only on the main tree, where /metadata/layout.conf says <update-changelog = true> The point remains, on overlays, where I'm using git, it creates broken manifests. Just for completeness, I also tried making the test overlay have <update-changelog = true> in the configuration. This is just a guarantee that the manifest WILL be wrong for *EVERYONE* who uses repoman, instead of just those who pass the parameter. Maybe its VCS dependent, but its certainly happening for me on Git. This should fix it: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=94aed24784d5122c5bbd7afd6dd85ee83c10ab2e This is fixed in 2.2.1. |