/srv/irclogs.ubuntu.com/2022/07/23/#lubuntu-devel.txt

kc2bez[m]Quickget, which is part of quickemu uses zsync for isos that support it.00:00
arraybolt3[m]And this begins the battle of the hypervisors.00:01
arraybolt3[m]s/this/thus00:01
kc2bez[m]Hahaha00:01
kc2bez[m]I like vim too ;) 00:01
arraybolt3[m]🤯00:01
arraybolt3[m]I tried that once, it was... well, a bit too much to learn at the time.00:02
arraybolt3[m]I'm still on Nano, Kate, and GEdit.00:02
arraybolt3[m](And VSCode.)00:02
kc2bez[m]I honestly very pragmatic. Use what works for you.00:02
arraybolt3[m]I would love to love Vim, and maybe one day I'll try it again. It was fun to learn.00:03
arraybolt3[m]<tsimonq2> "You can literally give it an ISO..." <- If it's a file:/// URL does that work?00:04
kc2bez[m]It takes some solid time in seat to get comfortable with anything.00:04
arraybolt3[m]True. My transition from hunt-and-peck typing to touch typing made me slow down dramatically, but now it's way faster.00:04
tsimonq2arraybolt3[m]: Yeah that too00:05
arraybolt3[m]**Really?** OK, I may just fall for Cockpit then, 'cause that was the one thing about virt-manager that finally drove me away - messing with storage pools when I had ISOs organized into a bunch of folders all over the place. (I mean, I might have migrated anyway, but that was one of the "OK, that's it, I'm done" problems.)00:06
tsimonq2My boss (Noah of asknoahshow.com and Linux Action Show) once described it like this in an IRL meeting...00:08
tsimonq2"People who look like you, have a beard, and write your code in Vim, probably use virt-manager or virsh. If you're 20 and graduated from college then you'll probably use Cockpit."00:08
tsimonq2LMAO00:08
arraybolt3[m]OK this is pretty cool so far.00:14
arraybolt3[m](Using Cockpit to test the new Calamares on Ubuntu Studio.)00:14
arraybolt3[m]Simon Quigley (Developer): Well, once again, you've earned a convert to your software setup.00:17
* arraybolt3[m] uninstalls GNOME Boxes00:17
arraybolt3[m]First Matrix and now Cockpit.00:17
kc2bez[m]> <@tsimonq2:linuxdelta.com> My boss (Noah of asknoahshow.com and Linux Action Show) once described it like this in an IRL meeting...00:20
kc2bez[m]> 00:20
kc2bez[m]> "People who look like you, have a beard, and write your code in Vim, probably use virt-manager or virsh. If you're 20 and graduated from college then you'll probably use Cockpit."00:21
kc2bez[m]I guess that is fairly true. I've used my share of virsh too. 00:21
arraybolt3[m]Simon Quigley (Developer): Hey, how close are we to looking over the Calamares SRU? (I hate to be in a hurry, but I won't be available after about 8:15, so if there's anything else that needs done to it, I'll need to know before then.)00:29
guivercrailer77gg00:31
arraybolt3[m]guiverc: ?00:31
* guiverc busy changing something 00:32
arraybolt3[m]Well, sadly, I'm back on GNOME Boxes. Cockpit kept pausing my VM mid-installation while I was fiddling with it, and the graphics were so bad (which sounds like not a big deal, but when the whole UI freezes while you're trying to install an OS in a hurry, it's a big deal). Sure looked cool, though, and I'll keep it around. Maybe it's just not for my particular computer.00:33
arraybolt3[m]Ubuntu Studio also installed and worked with Calamares 3.2.60.00:45
tsimonq2arraybolt3 @arraybolt3:matrix.org: Ready for roast time? 00:52
arraybolt3[m]OK.00:52
tsimonq2Why delete this debian/calamares.100:52
tsimonq2And this debian/calamares.manpages00:52
tsimonq2Just getting you warmed up...00:53
arraybolt3[m]Because Calamares upstream provides a manpage already.00:53
arraybolt3[m]Having two manpages for the same app in different spots could confuse the end user.00:53
tsimonq2Standard formatting of bug mentioning is (LP: #123456)00:54
ubot93Launchpad bug 123456 in xine-lib (Ubuntu) "podcast crashes amarok" [Undecided, Fix Released] https://launchpad.net/bugs/12345600:54
tsimonq2Surround with parentheses00:54
arraybolt3[m]Ah, didn't realize that. Fixing.00:54
tsimonq2You didn't create the signing key yourself, where did you get it from?00:54
arraybolt3[m]OK, so first I downloaded the asc file from upstream's GitHub. Then I used GPG to get the key ID, and pulled it from the keyserver, then exported it with "gpg --export --armour".00:55
arraybolt3[m]s/armour/armor/00:55
arraybolt3[m]I verified that it works using "uscan --download-current-version".00:56
tsimonq2Yes, so summarize that in the changelog please00:57
arraybolt3[m]OK.00:57
tsimonq2What's up with the weird differences between tabs and spaces in the copyright file?00:57
arraybolt3[m]Eh? Didn't notice those, I'll look at it.00:58
tsimonq2Oh your watch file flat out doesn't work00:58
arraybolt3[m](I copypasted copyright data from within Calamares itself, so that may be the problem.)00:58
arraybolt3[m]tsimonq2: Not possible, it works on my end.00:58
arraybolt3[m](uscan --download-current-version works.)00:59
tsimonq2End of line 3 of your changelog 00:59
tsimonq2s/changelog/copyright/00:59
arraybolt3[m]Hold on, looking at it, I'm not even seeing a tab.01:00
arraybolt3[m]Simon Quigley (Developer): Where is the tab? End of line 3 on the copyright, I'm not seeing anything weird in particular.01:01
lubot[telegram] <tsimonq2> https://matterbridge.lubuntu.me/d0347436/file_5637.jpg01:02
arraybolt3[m]Argh, just figured out how to get Nano to show them. My copypasting of copyright data for maximum accuracy backfired. Sorry, fixing...01:02
tsimonq2Also you are not consistent with comma vs not in the entries you add01:03
arraybolt3[m]That was a leftover from the previous copyright file, repair it?01:03
tsimonq2Instead of "fixed a flaw" in the changelog it should be a short summary of the flaw you fixed01:04
arraybolt3[m]Even though the summary is immediately underneath it?01:04
tsimonq2arraybolt3[m]: Yes, ONLY the ones you add though01:04
tsimonq2arraybolt3[m]: Same rationale for package descriptions in control01:05
arraybolt3[m]Hold on, going too fast, gimme a sec...01:05
tsimonq2One line summary then a couple lines below expanding01:05
tsimonq2All good01:05
arraybolt3[m]OK, back.01:09
arraybolt3[m]Simon Quigley (Developer): OK, I fixed everything you mentioned and pushed to Git.01:11
* tsimonq2 takes out Elon Musk's flamethrower01:11
tsimonq2We're not done here yet :P01:12
arraybolt3[m]Of course, but everything behind us is fixed.01:12
arraybolt3[m]Or burnt, depending on how you want to look at it :-P 01:12
tsimonq2Should be `SRU (LP: #929292).` with the period *after* :P and the period before your sub-bullet should be a colon.01:13
arraybolt3[m]Sub-bullet?01:13
arraybolt3[m]Like "- Reasoning:"?01:13
arraybolt3[m]Rather than "- Reasoning -"?01:13
tsimonq2If you use `Reasoning -` instead of a colon it may confuse some automation01:13
tsimonq2arraybolt3[m]: Yes01:13
tsimonq2But I mean at the end of the main bullet point line before your last sub-bullet01:14
arraybolt3[m]OK, ready for flamethrower.01:16
arraybolt3[m]Simon Quigley (Developer): ^01:16
tsimonq2Explain every part of the version to me and why you chose it01:16
arraybolt3[m]OK, hold on, pulling up docs so my reasoning makes sense...01:16
arraybolt3[m]According to the StableReleaseUpdates wiki page, "The version number does not conflict with any later and future version in other Ubuntu releases (the security policy document has a well-working scheme which can be used for SRUs.)" So I followed the link to the security policy document, and it said...01:17
arraybolt3[m]In the rare case of a new upstream release being pushed to all stable releases (substitute for 12.04 in the version string):01:18
arraybolt3[m]NOTE: This is for an upstream only update, not a backport of the development release package01:18
arraybolt3[m]=============  ================ ====================... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/1793947211645033369a27cf56876c3befc29f35)01:18
arraybolt3[m](Wow that's one ugly table.)01:18
arraybolt3[m]So I used that format. Upstream release is 3.2.60, and it is a new upstream release to 22.04, so it's now 3.2.60-0ubuntu0.22.04.1.01:19
arraybolt3[m](I am noticing a potential problem...)01:19
arraybolt3[m]Simon Quigley (Developer): ^01:19
arraybolt3[m]That was the only example the document provided for a new upstream release, and since it was an upstream-only update and not a backport of the development release package, that's what I used.01:20
tsimonq2arraybolt3[m]: What's the problem? I don't see one01:21
arraybolt3[m]It was "all stable release", this is going into Jammy only.01:22
arraybolt3[m](I mean, the formatting is for an update into all stable releases.)01:22
arraybolt3[m]So I'm wondering if maybe there's some different formatting for when it's only going into one stable release... or is it going into all stable releases?01:22
tsimonq2There is one other correct potential version 01:23
arraybolt3[m]Which is? (Sorry, I'm not figuring it out from the security updates doc.) Simon Quigley (Developer) 01:24
tsimonq2> <@arraybolt3:matrix.org> =============  ================ ====================... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/9004eb95b969fc7dd7157be7f58a4bd5e54f6def)01:25
arraybolt3[m]Ah, leaving off the .60. OK.01:25
arraybolt3[m]But we've included the minor version number before, so I think it should stay.01:25
arraybolt3[m](Indeed, we've never left the minor version number off that I can see.)01:26
arraybolt3[m]Simon Quigley (Developer): ^01:26
tsimonq2Nope01:27
tsimonq2Don't modify the upstream part at all01:27
tsimonq2You're simply removing the release version number 01:27
arraybolt3[m]Oh wait, I noticed the wrong part of your example.01:27
arraybolt3[m]So I should do that?01:28
arraybolt3[m](Removing the release version number?)01:28
arraybolt3[m](And now I finally see the spot in the document that shows where I can do that. OK, that satisfies all the rules I can see.)01:28
arraybolt3[m]2.0                           2.0ubuntu0.101:29
arraybolt3[m](Which looks like a typo in the document possibly? Now I'm really confused. I'm just going to do what you said and go with it.)01:30
arraybolt3[m]Simon Quigley (Developer): OK, pushed to Git again and awaiting the next needed fix.01:33
tsimonq2LGTM. Did you get to the SRU paperwork yet?01:35
arraybolt3[m]Simon Quigley (Developer): Not yet, and sadly, due to extenuating circunstances, I don't actually have the time to do that (I have to leave in about 5 minutes). It is awful if I leave that for you?01:35
tsimonq2arraybolt3[m]: We can shoot for Monday to get you practice 01:37
arraybolt3[m]OK, sounds good. Sorry to run out of time just at the very end.01:37
tsimonq2All good01:37
arraybolt3[m]Whew, that was a lot! Thank you for teaching me all that, that was awesome. \o/01:38
tsimonq2Of course :)01:46
lubot[telegram] <lynorian> I don't know I ever quite groked how translations worked07:57
lubot[telegram] <teward001> the translations platform we wanted to set up a long while ago couldnt be set up due to infra restrictions at DO and then because CI ate everything it exhausted my resources too17:28
lubot[telegram] <teward001> so we never really set up a translations platform that worked17:28
lubot[telegram] <teward001> then Simon went awol and it went into the depths so :P17:29
lubot[telegram] <profetik777> sup folks...i installed the daily and enabled non-released updates....so if you need someone to test some thing on intel based hardware, lemme know17:44

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!