Olivier Berger <[email protected]> writes: > Package: src:org-mode > Severity: whishlist > > Dear Maintainer, > > I'm trying to figure out whether there are any pending changes upstream > to solve a bug that may be fixed upstream.
Do you know how to use git? If so, I could make this easier to set up for org-mode. The worst-case scenario interface would be: $ debcheckout org-mode && cd org-mode $ # The new command to fetch the upstream remote using upstream/metadata $ git log upstreamvcs/main [ Press "/" key, type "tag" <Enter/Return>, repeat until you find the version we use in Debian ] [ Press the up arrow to read commit messages in chronological order. ] I would have to look into if git-build-package's upstream tag associating support will still work properly with dfsg-cleaned source --using this tag association feature would make comparing their source to our source easier. > It seems that upstream's elpa or melpa provide versions of the packages, > and there, versioning is like 20161224. However there's nothing in > /usr/share/doc/org-mode/ that indicates a corresponding date. "A few weeks ago GNU-devel ELPA and NonGNU-devel ELPA also switched to the RELEASE.0.DATE.COUNT format", and MELPA is finally going to move to this git-describe style too (https://emacsair.me/2026/07/03/melpa-channels/). This type of version number is something we already use in Debian so that apt can correctly determine the latest version. > Having some kind of upstream changelog comparable to upstream's could > help also. I'll reply to this point in a moment, because I want to CC upstream about it. Best, Nicholas
signature.asc
Description: PGP signature
