libera/#devuan-dev/ Saturday, 2023-01-07

hagbardWhat's the best practice for merging debian changelogs into devuan?09:47
hagbardThe package has a changelog entry for forking. Then there are later debian changes. Now i'm merging the debian changes into the the devuan fork.09:49
hagbardDo i do it in this order?: 1.1devuan1 "fork for devuan blah blah"; 1.2 "change in debian, another change in debian, yadda, yadda"; 1.2devuan1 "Merged 1.2 into devuan"09:52
bb|hcbhagbard: As per me the purpose of the changelog is for people to easily get a summary of the important changes, and merging the changelogs seems as a good idea. The alternative is to list the changes in the last entry, but then the reference to the respective debian version will be lost11:29
hagbardpushed the merge to https://git.devuan.org/devuan/fluidsynth/src/branch/suites/unstable . Does anyone like to review, before I trigger a build?11:48
bgstack15hagbard: for the small handful of packages I maintain, I always rebase my commits on top of the latest debian/master branch (well, for suites/unstable, of course). So I always just add my one [almost unchanged] changelog entry on top of the whole d/changelog14:45
bgstack15Nobody's chewed me out yet.14:46
bb|hcbhagbard: The upstream/3.2.1 tag is not pushed (you will get gbp:error: upstream/2.3.1 is not a valid treeish); standarts are now 4.6.2 (ignore lintian insisting on 4.6.1); you can add debian-watch-does-not-check-openpgp-signature to debian/source/lintian-overrides19:39
bb|hcbAbout standards, there is a checklist -19:40
bb|hcbhttps://www.debian.org/doc/debian-policy/upgrading-checklist.html19:40
bb|hcbTo check yourself all the stuff reported, you can use lintian --pedantic --show-overrides --tag-display-limit=0 -E -I (assuming you build on updated ceres)19:42
bb|hcbHTH :)19:42
hagbardyes, I forgot to push the tags *sigh*21:59

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!