Package: bugs.debian.org

My package has a mergeing history, and bugs.debian.org has become
confused.

The real history is like this:

                                       4.2
                                       sid
                                        +
                        .............../|
                       /                |
                    3.13                |
                 sid/stretch            |
                      |                4.1
                      |             experimental
                      |                 +
                      | .............../|
                      |/                |
                    3.12                |
                 sid/stretch            |
                      |                 |
                 fix-#867185            |
                      |                 |
                    3.11                |
                 sid/stretch            |
                      |                4.0
                      |            experimental
                      |                 +    `
                      | .............../      `
                      |/                       `
                    3.10                [previous experimental
                 sid/stretch              versions 0.22.*]
                      |
                      |
               [previous sid/stretch
                 versions 3.*, 2.* etc.]

When I look at my changelogs, I have not been consistent about the
ordering of entries when I make a merge.

The result in the BTS is this:

  https://www.chiark.greenend.org.uk/~ijackson/2018/bts-merges/graph.png
  https://www.chiark.greenend.org.uk/~ijackson/2018/bts-merges/more-graph.png
  https://www.chiark.greenend.org.uk/~ijackson/2018/bts-merges/full-graph.png
  https://www.chiark.greenend.org.uk/~ijackson/2018/bts-merges/bug.html

The BTS-produced graph is really not very true.

I was prompted to look at this because the BTS graph caused the
testing autoremoval logic to think that #867185 meant 3.13 ought to be
removed.  This started to happen when I uploaded 4.2, so it must have
been caused by 4.2's changelog.  (I have worked around the problem by
adding some more version tags.)


I think that the most likely root cause is my changelog structure,
but it is also possible that there is a bug or infelicity in the BTS.

How should developers write their changelogs ?  In particular, when
merging, what order should the merged entries be in ?

(If the BTS is inferring a total order from the changelog in sid, then
it is wrong, because the actual version structure is only a partial
order.  But the revision graphs it outputs suggest it's not a total
order...)


I looked here:

   https://www.debian.org/Bugs/Reporting
   https://www.debian.org/Bugs/Developer
       searched in pages for "version", "found", "fixed"

   https://www.debian.org/doc/debian-policy/#debian-changelog-debian-changelog

I would also have spotted a hint on the full-size version graph page,
probably.


FYI full git history of my package (as far as Debian is concerned) is
here:
   https://browse.dgit.debian.org/dgit.git/
   https://git.dgit.debian.org/dgit


Thanks,
Ian.

--
Ian Jackson <ijack...@chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.

Reply via email to