Summary: | repoman should not generate new ChangeLog entry when modifying Manifest | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Markos Chandras (RETIRED) <hwoarang> |
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: | 402213 |
Description
Markos Chandras (RETIRED)
2012-01-07 12:21:35 UTC
Until this is fixed, use --echangelog=n when re-manifesting. I vaguely recall that this was done because the Council decided that all changes to a package should be recorded, and fixing the Manifest is also such one. (echangelog did the same IIRC) (In reply to comment #2) > I vaguely recall that this was done because the Council decided that all > changes to a package should be recorded, and fixing the Manifest is also such > one. (echangelog did the same IIRC) Fabian, I am 95% sure that remanifests were never documented (at least for the majority of devs) in the Changelog. It is a trivial change which does not need0 any sort of documentation on the Changelog. I think echangelog did not do that, it simply said something like "no changes spotted. Use --force to write a changelog anyway" I really don't care much. I just think Portage should follow Council decisions. Bug 388997 seems to be complaining about the same behavior. I think it's reasonable skip ChangeLog generation when only the Manifest is modified, and allow --echangelog=force to for generation. Currently, --echangelog=force only applies to the case where the ChangeLog is already modified prior to calling repoman. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=e96a703a6d1e27681b0982c05d8d1389a035254d This is fixed in 2.1.10.46 and 2.2.0_alpha86. |