libera/#devuan-dev/ Wednesday, 2022-09-07

rrqok everyone: I'm not drowning in reports about how tje ugraded ISOs work ... which ISO did you try, and which use cases? did it work as expected, or does something need fixing?00:03
rrq... I'll be filling out https://ido.rrq.id.au/download/usecases.html00:04
rrq.. for convenience I'v added numbering of use cases: eg B06 is the "beowulf + server, network" use case.00:18
golinuxHow/where can I make a comment about the pad? and is it possible to get line # on rich text?02:50
golinuxThe apology para seems out of place in its current location.without line #, suggesting an alternate location would be difficult . . .02:53
golinuxOverall, I think it is quite well written and that is the only thing I really stumbled over.02:54
golinuxWill take another look later or tomorrow.02:55
golinuxHere's one more. Passive tense really sucks. Instead of "* A policy has been implemented to ensure . . ."04:04
golinuxTry . . . "*We have implemented a policy to ensure . . ."04:05
Xenguygolinux, Why not just modify the pad directly?06:39
golinuxBecause I don't like to make unilateral decisions07:01
brocashelmwhat i've seen looks good so far. i would just add a small section towards the bottom with the proposed changes. comparing original vs. your revision07:10
Xenguygolinux, I agree I don't really grok the history/changes that well with the current pad, but I just went ahead and made improvements as I saw fit, assuming that there was some 'history' being tracked somewhere if there was a real need to revert...07:18
XenguyI'd say just go for the edit if you have a strong sense it improves the statement07:18
XenguyIt does appear some 'history' of changes is tracked, I just didn't see how to display it optimally yet07:19
joerg>>[6 Sep 2022 21:20:06] <lts> I did refresh, still says "rsa4096 2017-09-04 [SC] [expires: 2023-09-03]"<< >>LESSONS LEARNED ... :<< avoid extending expiry dates to only change last digit of year only. Not recognizing the change s/2022-09-03/2023-09-03/ was a recurring avoidable oopsie that could esily get mitigated by s/2022-09-03/2023-10-11/10:07
joerggolinux: I just added a comment on your behalf, I didn't find an option to automatically have line numbers to refer to but the comment feature seems to do the trick to refer to a particular position in text. For further convenience we might tag our comments with a timestamp/number or other unique ID10:39
XenguyYes, comments might work, and I didn't see an option to number lines either11:05
joerg>>[7 Sep 2022 07:19:33] <Xenguy> It does appear some 'history' of changes is tracked, I just didn't see how to display it optimally yet<<  File menu, "display the document history". It seems "esc" key makes the timeline vanish again, and keeping chat and timeline and comments visible concurrently is tricky11:24
XenguyOkay thanks11:27
joergworks?11:28
XenguyI'll need to try later on11:28
joerghttps://i.imgur.com/JfTFiaW.jpg  https://i.imgur.com/g3DxR25.jpg  https://i.imgur.com/q7HBJJN.jpg  https://i.imgur.com/4h5pwcB.jpg  https://i.imgur.com/B0M8wrV.jpg11:46
joergmissing this feature https://i.imgur.com/Hg1sFEJ.jpg12:53
joergfrom https://archive.flossmanuals.net/etherpad/_all.html12:53
joergwithout this, I think it's not feasible to repeatedly re-read the complete document to spot the differences. btdt, didn't work for me13:11
joerghmmmm  https://i.imgur.com/O6zlrMq.jpg  https://pad.dyne.org/settings/#cursor13:23
joerghttps://i.imgur.com/899Ccuq.jpg   https://i.imgur.com/60jAX3h.jpg   for probably obvious reasons this feature doesn't work for "Rich Text" documents? Seems to work e.g. for "code" documents since "code" is plain ascii I guess13:46
bgstack15Devuan meet tomorrow, September 8, at 20:30 UTC. Pad is here: https://pad.dyne.org/code/#/2/code/edit/t1EW9iaqHDCcXkz0RNPKWw7W/17:38
fsmithredI uploaded new desktop-live isos to fdo. I hope to do the minimal-live isos later today.18:17
fsmithredafk. bbl.18:17
bb|hcbI just came to know that the package is not signed at all: http://paste.debian.net/1253097/19:36
fsmithredcan we sign the key locally and push to a keyserver?19:40
fsmithredor does it need to be signed with the previous key?19:40
bb|hcbSigning the key is another story. The package (.deb) is not signed19:46
bb|hcbI have already pushed the current key to several keyservers19:47
bb|hcbrrq just extended the validity of the old key; that was the best fast solution option, because else we would need to change lots of stuff in dak/amprolla configs19:48
fsmithredgotcha19:48
bb|hcb... and as a short-term fast measure that was the best to do19:50
onefangSo we have to wait for LeePen for a proper long tern solution?20:02
bb|hcbI never did dig deep into that part - Debian packages are also not signed themselves, but the repo data  contains checksums of the packages20:02
bb|hcbonefang: I'd suppose that extending the key more for chimaera is one thing to do; next one is to be decided (and hence we would better wait for LeePen) if the current key will be used for daedalus or a new one will be generated (I have no idea if amprolla supports multiple keys at all)20:04
onefangWe also gotta worry about the older releases.  Stretch LTS reached EOL couple of months ago, so I guess ASCII is EOL now, but Beowulf isn't.20:08
bb|hcbFor the old releases, we'd better push the same key with extended validity20:09
fsmithredwhat key does archive.devuan.org use?22:50
bb|hcbfsmithred: E032601B7CA10BC3EA53FA81BB23C00C61FC752C (the same one that expired)23:12
fsmithredthanks23:22
fsmithrednew desktop-live and minimal-live isos are up.23:23

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