libera/#devuan-dev/ Monday, 2022-11-28

hagbardHmm, dak@devuan.org sends mail with charset="ANSI_X3.4-1968", and has package metadata in the body that's originally utf-8. This sometimes causes some mojibake.20:06
hagbardAny opinions on forking kexec-tools to close #614, #714, #715? (bugs due to broken init script). Patches for the script exist in the debian bug tracker, but don't get applied in/by Debian. Should I do it for Devuan?20:14
LeePen#614 is gnome-keyring?20:22
LeePenMy inclination is to leave #714/5 to Debian.20:22
LeePenBut others may differ.20:22
LeePenIt is more the ongoing mantenance than the time to do the initial fork.20:23
LeePenBut, if you are up for that, I wouldn't want to stop you.20:23
LeePenIf you do want to take on kexec-tools, the package looks in poor shape generally.20:24
hagbardOh, sorry, #615, not #61420:25
LeePenSome of the other Debian bugs need attention: https://bugs.debian.org/src:kexec-tools20:26
hagbardI agree that a broken init script should be fixed in debian. But at the other hand, that's not happening.20:27
LeePenI suppose I could nmu it in Debian, maybe that is a better solution.20:28
hagbardSeems to be a good idea.20:28
LeePenI'll try to get round to it. Knee deep in seatd/consolekit/sway atm.20:29
hagbardI would be able to fix the init script, but I would not be able to fix the more serious bugs from the debian tracker, e.g. FTBFS on risc64 would be a bit far off from my home turf.20:30
LeePennw. I hope you don't think I am being discouraging. What you are doing is great!20:36
hagbardDifferent topic: I sifted a bit through the devuan bug tracker, and found one that can be closed since it already solved itself.  #331 User wanted a newer version packaged, and that has already happened long ago.20:46
LeePenhagbard: Great. If you email 331-done@bugs.devuan.org with and explanation and version pseudoheader, that will close it.20:49
hagbarduhm, version pseudoheader?20:52
LeePenVersion: <fixed-version>20:53
LeePenat the top of the email body.20:53
hagbardah, ok20:54
LeePenhttps://bugs.devuan.org/Developer.html20:54
hagbardthx20:56
LeePenOur builds do that automatically if d/changelog has the correct (Closes: #NNN).20:57
LeePenBut, if helps to record the version for manually closed bugs.20:57
hagbardsent.21:19
hagbardsince I'm dabbling with devuan packaging lately, is there a dev/maintainer mailing list I should subscribe to?21:30
rrqhmm, re ANSI_X3.4-1968 .. that probably originates with an LC_ALL=C setting in some scripting21:51
bb|hcbANSI_X3.4-1968 sounds really cryptic21:56
bb|hcbBTW. I have seen on Debian channels that there is a bot that responds to bugs mentioned with the bug subject21:59
LeePenMany use zwiebelbot22:11
LeePenThink there is also KGB22:13
bb|hcbhttps://github.com/weaselp/ticketbot - looks like zwiebelbot is based on this22:16
golinuxhagbard: Are you on the devuan-dev mail list? https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/devuan-dev22:27
hagbardnow i am22:33
golinuxhagbard: Great!22:36
golinuxWe also have weekly face-to-face jitsi meets every Thursday @20:30 UTC. Announcement is posted weekly on our dev channels.22:37
bb|hcbhagbard: It is a good idea to add you key to Devuan's keyring, do a PR at https://git.devuan.org/devuan/devuan-keyring22:52
LeePenhagbard can you pastelink the headers of the email ?22:54
hagbardbb|hcb: k, will do22:56
hagbardLeePen: Which email? The one with the b0rked encoding? Or the one that I sent to the bug tracker?22:59
bb|hcbThe one with us-ascii encoding23:01
hagbardThere it's visible: https://bugs.devuan.org/cgi/bugreport.cgi?bug=724#1023:02
hagbardor more precisely, there: https://bugs.devuan.org/cgi/bugreport.cgi?bug=724;msg=1023:03
bb|hcbAnd here it was ok: https://bugs.devuan.org/cgi/bugreport.cgi?bug=670;msg=2523:11

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