You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for tip! I just skimmed through related conversations from a while ago, most notably in #29, and found out the following:
Even though this is a pure Debian project, we chose the format "quilt" over "native".
This means all downstream Debian releases are based on the latest upstream source release on GitHub.
To track downstream changes separately (i.e. any changes to debian/*) files in the same repo as upstream, we use the "debian" branch.
This is currently not enforced nor documented.
So, I think, -b debian in the Vcs-Git is correct, because it informs the tracker about new downstream changes, but unfortunately, the information is prone to become outdated.
I'm not sure how to best fix this. For now, I just updated the debian branch and will leave this issue open.
Maybe the simple answer is to just track upstream and downstream in the same branch, given that in reality there is no separate development. So, yeah, maybe just remove -b debian in d/control.
Either the debian branch is not updated, or the Vcs-Git entry in debian/control needs the "-b debian" part removed.
The text was updated successfully, but these errors were encountered: