rrq | ok 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.html | 00:04 |
rrq | .. for convenience I'v added numbering of use cases: eg B06 is the "beowulf + server, network" use case. | 00:18 |
golinux | How/where can I make a comment about the pad? and is it possible to get line # on rich text? | 02:50 |
golinux | The apology para seems out of place in its current location.without line #, suggesting an alternate location would be difficult . . . | 02:53 |
golinux | Overall, I think it is quite well written and that is the only thing I really stumbled over. | 02:54 |
golinux | Will take another look later or tomorrow. | 02:55 |
golinux | Here's one more. Passive tense really sucks. Instead of "* A policy has been implemented to ensure . . ." | 04:04 |
golinux | Try . . . "*We have implemented a policy to ensure . . ." | 04:05 |
Xenguy | golinux, Why not just modify the pad directly? | 06:39 |
golinux | Because I don't like to make unilateral decisions | 07:01 |
brocashelm | what 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 revision | 07:10 |
Xenguy | golinux, 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 |
Xenguy | I'd say just go for the edit if you have a strong sense it improves the statement | 07:18 |
Xenguy | It does appear some 'history' of changes is tracked, I just didn't see how to display it optimally yet | 07: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 |
joerg | golinux: 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 ID | 10:39 |
Xenguy | Yes, comments might work, and I didn't see an option to number lines either | 11: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 tricky | 11:24 |
Xenguy | Okay thanks | 11:27 |
joerg | works? | 11:28 |
Xenguy | I'll need to try later on | 11:28 |
joerg | https://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.jpg | 11:46 |
joerg | missing this feature https://i.imgur.com/Hg1sFEJ.jpg | 12:53 |
joerg | from https://archive.flossmanuals.net/etherpad/_all.html | 12:53 |
joerg | without this, I think it's not feasible to repeatedly re-read the complete document to spot the differences. btdt, didn't work for me | 13:11 |
joerg | hmmmm https://i.imgur.com/O6zlrMq.jpg https://pad.dyne.org/settings/#cursor | 13:23 |
joerg | https://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 guess | 13:46 |
bgstack15 | Devuan meet tomorrow, September 8, at 20:30 UTC. Pad is here: https://pad.dyne.org/code/#/2/code/edit/t1EW9iaqHDCcXkz0RNPKWw7W/ | 17:38 |
fsmithred | I uploaded new desktop-live isos to fdo. I hope to do the minimal-live isos later today. | 18:17 |
fsmithred | afk. bbl. | 18:17 |
bb|hcb | I just came to know that the package is not signed at all: http://paste.debian.net/1253097/ | 19:36 |
fsmithred | can we sign the key locally and push to a keyserver? | 19:40 |
fsmithred | or does it need to be signed with the previous key? | 19:40 |
bb|hcb | Signing the key is another story. The package (.deb) is not signed | 19:46 |
bb|hcb | I have already pushed the current key to several keyservers | 19:47 |
bb|hcb | rrq 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 configs | 19:48 |
fsmithred | gotcha | 19:48 |
bb|hcb | ... and as a short-term fast measure that was the best to do | 19:50 |
onefang | So we have to wait for LeePen for a proper long tern solution? | 20:02 |
bb|hcb | I never did dig deep into that part - Debian packages are also not signed themselves, but the repo data contains checksums of the packages | 20:02 |
bb|hcb | onefang: 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 |
onefang | We 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|hcb | For the old releases, we'd better push the same key with extended validity | 20:09 |
fsmithred | what key does archive.devuan.org use? | 22:50 |
bb|hcb | fsmithred: E032601B7CA10BC3EA53FA81BB23C00C61FC752C (the same one that expired) | 23:12 |
fsmithred | thanks | 23:22 |
fsmithred | new 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/!