2013/4/22 Andreas Jaeger <aj@suse.com>:
Why are you removing content from the changes file? Pretty-printing is fine but removing the 1.0.5 entry loooks wrong.
I'm not removing content. The update was done in two steps in one branch (first 1.0.5 and then 1.0.6), and in one step in another branch. Hence the changelog slightly differs.
So, I complain about these two lines *missing*: - Changes from version 1.0.5: + Improves error handling; fixes failing test.
I'm sorry, this 2nd line is clearly there, the first one is missing indeed,b ut there is a reason (see above).
The general rule is that no information should be lost
Where is that rule coming from? The general rule that I remember is that there should be *regressions* and that no *fixes* should be lost, which roughly means "no regressions to bnc#/FATE#, as long as they're applicable"
and it could be that some of the Folsom packages contained other changes that were not done to the Grizzly ones.
I agree, that can happen, but that means we'd need to take a look at the actual diff (e.g. the one outside the .changes file) and not the .changes file. or do you trust that if an entry is in the .changes file that it is actually also in the .spec file?
Looking at https://build.opensuse.org/request/show/172713, the Folsom branch contains an extra patch that is not in the Grizzly one. Is this really intended?
Please check the .changes file diff, it explains it: -Wed Mar 6 14:01:15 UTC 2013 - vuntz@suse.com -- Add compat-newer-requests.patch: take patches from upstream to - allow working with newer versions of python-requests. vs +------------------------------------------------------------------- +Mon Feb 18 09:49:46 UTC 2013 - dmueller@suse.com + +- remove keystoneclient-requests-compat.patch: + * Merged upstream Yes, there is a time difference, but thats because we were working on different branches, and one branch was getting the fix quicker than the other one (it was not clear that the other one actually needs it until our continuous integration system told us about it). Greetings, Dirk -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org