http://bugzilla.suse.com/show_bug.cgi?id=1001636
http://bugzilla.suse.com/show_bug.cgi?id=1001636#c5
--- Comment #5 from Lee Duncan
(In reply to Lee Duncan from comment #2)
As I study this situation, I see a fatal conflict in logic.
The *.changes file in each distribution are supposed to be strictly reverse chronological, i.e. new entries always added a the head of the file, with a proper date/time tag.
If this is true, then how can the target-isns.changes file in openSUSE:Factory and in openSUSE:Leap:42.2 ever be the same once they have diverged? Currently, these two packages have different "*.changes" files.
I do not know how you wish this blocking issue resolved. Please let me know.
PrjM of the various products (SLE, Leap, Tumbleweed) are well aware of this - and in light of getting things in sync have accepted many exceptions here.
What we keep value on is that bug refs do not get lost (even if moved to a different point in the .change where they might also apply)
Especially if you look at the diff between SLE12 and Leap one would assume it should be possible to align those two (TW will be more complex)
osc rdiff SUSE:SLE-12-SP2:GA target-isns openSUSE:Leap:42.2
I will be glad to (1) cancel my recent request to update Leap 42.2, and (2) submit the patch you mention for this bug to SLE 12 SP2, so that it exactly matches Leap 42.2, if you wish. Or ... I can update Leap 42.2 and SLE 12 SP2 to the same bits as factory. I just would like to know, ahead of time, which one has the better chance of being accepted. -- You are receiving this mail because: You are on the CC list for the bug.