Re: Best practices for Debian developers who are also upstreams?
Otto Kekäläinen <otto@seravo.fi> writes:
> Hi!
>
> Thanks for the example. I see you even maintain the changelog in upstream:
> https://git.notmuchmail.org/git?p=notmuch;a=blob;f=debian/changelog;h=4f7457cd7f588e6d3a821bf1530cc1f8742c8d6f;hb=refs/heads/master
Yes.
>
> But apparently "upstream" releases are decoupled from also bumping the
> Debian version?
>
> https://git.notmuchmail.org/git?p=notmuch;a=commit;h=3efa2ad72c8ffd8183fab2cd6592f35e72fbb7d7
>
> This means debian/changelog shows "wrong" version at least for one commit
> and that would not work in the CI pipelines I use as build products would
> end up with inaccurate version strings. This is something I seek to find an
> elegant solution for..
We're obviously less focussed on CI than you are. The fact that it takes
a couple commits to make a release has never been problematic for us. I
guess if it was important, you could do all the version updates in one
commit.
d
Reply to: