=== guiverc2 is now known as guiverc [01:56] https://www-muylinux-com.translate.goog/2022/07/18/lubuntu-backports/?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en&_x_tr_pto=wapp phenominal [02:06] Not sure that we originally intended to take a Neon-like approach, but then again I don't have anything against it. Why not? Especially if we distribute an extra ISO with Backports enabled by default. [02:09] Yeah, that's the only part of the article I was like "mehhhhhhhhh" [02:10] Do you mind if I reply to your RFC on the lubuntu-devel and lubuntu-council lists? [02:10] Simon Quigley (Developer): ^ [02:10] I do intend to copy both lists on the reply. [02:13] -queuebot:#lubuntu-devel- New binary: libfm-qt [amd64] (kinetic-proposed/universe) [1.1.0-2~1] (lubuntu) [02:13] -queuebot:#lubuntu-devel- New source: lubuntu-installer-prompt (kinetic-proposed/primary) [0.2.0-0ubuntu1] [02:14] That's what it's there for :) [02:30] 👍️ [03:03] Dan Simmons @teward001 arraybolt3 guiverc Rober Leo K @lynorian @The_LoudSpeaker - please read https://lists.ubuntu.com/archives/lubuntu-devel/2022-July/001930.html [03:03] [telegram] @Leokolb @Roberalz ^^^ [03:04] ack [03:04] [telegram] ack [03:05] ack [03:05] ack [03:08] PLEASE NOTE: All times are in US Central (UTC-5) [03:09] tsimonq2: guiverc Leo K Rober ^^^ [03:13] tsimonq2, the website may make allowances for local time; eg. when I look at the page it reports as GMT+1000 & says Australia/Melbourne date/times [03:14] * arraybolt3[m] is still trying to figure out how on earth to use a Doodle poll... [03:15] ahhh nice guiverc [03:15] [telegram] same [03:16] [telegram] tsimonq2: no way in *hell* are you going to be available 24/7. *points at your bad times* [03:16] I will be available for any time the standup occurs :P [03:18] Ok, I think I finally figured it out. 🤞 [03:18] [telegram] *literally pushes tsimonq2 into the padded room to get some rest* [03:18] !cookie | @teward001 [03:18] @teward001: Wow! You're such a great helper, you deserve a cookie! [03:19] SLEEP IS FOR THE WEAK, I ONLY DRINK BANG [03:19] https://www.youtube.com/watch?v=THN73gP786c [03:20] Reminds me of that anti-smoking commercial where they have the "With 100 times the carbonation of ordinary soda, Splode is intense!" It ends with the last can of soda exploding and the person who opened it vanishing, then says, "Only one product kills 1 in 3 people who use it - Tobacco." [03:21] [telegram] *cough* https://www.youtube.com/watch?v=2UOYvcSy2f4 (re @lubuntu_bot: (irc) SLEEP IS FOR THE WEAK, I ONLY DRINK BANG) [03:28] OK, interesting. Adding the backports PPA on a freshly installed system (before even installing the initial OS updates) and then doing "sudo apt update && sudo apt upgrade" results in lots of packages held back. [03:28] (Probably because of the updated sonames I'm realizing.) [03:29] [telegram] also because additional dependencies [03:29] [telegram] upgrade won't install packages that have additional dependencies [03:29] True. I was just trying to reproduce that issue from earlier. [03:29] [telegram] full-upgrade or dist-upgrade will install *every package* that's pending including dependencies [03:29] [telegram] there was an issue earlier? [03:30] @teward001: Yeah, lemme dig it up... [03:30] @teward001: https://pastebin.com/fqh2UwXm [03:31] This is from a user called panuweb from earleir. [03:31] s/earleir/earlier/ [03:45] [telegram] ye that's going to be because soname bump. you'll have to rebuild the entire stack of apps each time [03:45] [telegram] which is why Backports are inherently 'unsupported' and will break things [03:56] "@teward001: https://pastebin.com..." <- Those env vars and package versions have me SO confused. [03:56] Line 21 [03:57] [telegram] ... what env vars [03:57] [telegram] those aren't env vars [03:57] You're right, something's fishy there. [03:57] [telegram] those're excerpts from the apt history.log file [03:57] lxqt-panel 1.1.0-5??? [03:57] [telegram] oh that [03:57] * arraybolt3[m] checks Launchpad [03:57] [telegram] i'd like to see what apt cache policy says about lxqt-panel [03:57] [telegram] apt-cache policy * [03:58] It should be 1.1.0-0ubuntu2~ppa1 [03:58] At any rate, I couldn't reproduce the problem in a VM on my end, and I tried twice, so... [03:58] [telegram] i'll bet you they're using Debian and not Ubuntu [03:58] @teward001: NSS, I said those two as separate items ;) [03:58] [telegram] or using Debian repos [03:58] * arraybolt3[m] checks Debian [03:58] [telegram] *pushes Simon into the abyss anyways* oops [03:58] See also 126-EOF [03:59] [telegram] *sips his steamed milk steamer with vanillaflavor instead* [03:59] Nah, latest version in Experimental in Debian is 1.1.0-1 (so says the tracker) [03:59] [telegram] (is midnight here) [03:59] [telegram] see now i want to see their apt sources.list [03:59] [telegram] and apt-cache policy outputs [03:59] So where on Planet Cyberearth did they find a 1.1.0-5?!?!???!!????! [03:59] [telegram] because it SOUNDS like they have chaos going on [04:00] [telegram] self-compiled crap maybe? (re @lubuntu_bot: (irc) So where on Planet Cyberearth did they find a 1.1.0-5?!?!???!!????!) [04:00] They might be using Debian and trying to build the packages themselves like Debian says if you're gonna use an Ubuntu PPA. [04:00] Hmm... I've seen that once before [04:00] Hold the phone [04:00] * arraybolt3[m] throws the phone [04:00] at teward001 [04:01] [telegram] there's a rule that I use for yelling at people: If you mix Debian and Ubuntu or Mint and Ubuntu or other flavors of Ubuntu and Debian and non-official-flavors, you did it wrong and have broken your system so. [04:01] https://lxqt-project.org/blog/2022/05/06/latest-lxqt-debian-ubuntu/ [04:01] [telegram] and then i propmtly yell xD [04:01] [telegram] oh wow they're using lxqt-project's repos [04:01] [telegram] well that's gonna deffo break with the backports [04:01] https://launchpad.net/~severusseptimius/+archive/ubuntu/lxqt [04:01] [telegram] because that includes *all* the LXQt libraries [04:01] [telegram] time to tell the user they dun goofed [04:01] Sure enough. [04:01] yeah and they use Debian revisions so that definitely directly conflicts with the archive LOL [04:01] That's not the Lubuntu Backports PPA. [04:01] [telegram] yep yep [04:01] https://lxqt-project.org/blog/2022/05/06/latest-lxqt-debian-ubuntu/ [04:02] Someone want to tell upstream they're a doofus for recommending that PPA? [04:02] * tsimonq2 isn't on the LC anymore, that's above my pay grade :P [04:02] [telegram] we should put a disclaimer on the Lubuntu Backports PPA and page: "THIS IS NOT GUARANTEED TO WORK IF YOU USE ANY OTHER PPAS FOR YOUR APPLICATIONS OR LXQT STUFF" [04:02] Maybe they tried to install both PPAs? [04:02] [telegram] tsimonq2: you're on the debian lxqt team and Lubuntu release manager after the recent votes, go yell at them yourself [04:02] * Eickmeyer[m] uploaded an image: (188KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/IGrOJngitNsYIkQtCdguvXoQ/image.png > [04:02] Perhaps the LXQt PPA works just fine on its own, and Lubuntu Backports works just fine on its own, but mix the two and they go boom? [04:02] [telegram] i need sleep so. *offlines* [04:02] Eickmeyer: Ey! [04:03] * arraybolt3[m] didn't do that [04:03] * tsimonq2 doses @teward001 with 10 grams of melatonin [04:03] night night [04:03] Night @teward001 [04:03] [telegram] actually lower doses are quite effective,i take 5mg melatonina night :P (re @lubuntu_bot: (irc) doses @teward001 with 10 grams of melatonin) [04:03] Imagine mixing PPAs of different packages not breaking things. [04:03] [telegram] with doc approvals of course. [04:03] [telegram] anyways, nini [04:03] lubot: I take 3 but at one point was up to 10 mg [04:04] Okay, come on guys, let's not roast them that hard. [04:04] Like, I know, should be a no-brainer. Some users are just like that though, lol. [04:04] Learning curve. We've all been there. [04:04] Yeah, just jaded. [04:05] https://imgflip.com/i/6nf34y [04:07] So, I know the backports is the new, shiny hotness, but where are we with the Cala SRU? [04:07] (Probably should've made it more clear by putting "Aaron" somewhere on the guy) [04:07] Eickmeyer: One moment, I'll pull it up. [04:07] https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1980180 [04:07] Launchpad bug 1980180 in calamares (Ubuntu Jammy) "[SRU] Calamares 3.2 Series for 22.04 LTS" [Medium, New] [04:08] I, for one, don't know how to directly answer Brian's question. [04:08] https://github.com/lxqt/lxqt/discussions/2281 [04:09] Eickmeyer: The only real way I can think to answer is to do two installs, one with the old Calamares, one with the new, then diff -r the two installs and see what happens. [04:09] That will objectively tell us how different the results are. [04:09] arraybolt3: The problem there is that we have no way of testing that afaik. [04:10] Because we'd have to see the .iso image as well. [04:10] Eickmeyer: Sure we do. Package Calamares 3.2.60, throw it in a PPA, and have me install it in a live env. [04:10] Then I'll do the install with it. [04:10] We've done similar tricks in Kinetic. [04:10] Am I the only one that knows how to answer Brian's question? Looked at it and started typing a response :P [04:10] Simon Quigley (Developer): You're uniquely qualified here as you understand the inner-workings of Calamares better than anyone else. [04:11] You're going to hate my answer... [04:12] We need to look at all of the changelogs for the in-between versions and determine whether any of those feature changes required configuration changes. Configuration changes easily means that the way the installer interacts with the end system has changed. [04:13] * arraybolt3[m] throws the phone again [04:13] So the real question is not, what does the Calamares update change? It is, do we need any settings changes in order to update to the new version, and if so, what are they? [04:13] Oh, OK. That makes sense. [04:13] * arraybolt3[m] picks the phone back up - that wasn't as bad as I thought [04:14] Okay, hold on, he's also asking a more general question. Think about this... [04:15] All Calamares really does is copy the squashfs over and do a bunch of changes to the host system to make that squashfs work [04:16] You could probably do a diff between the resulting partitions. Gonna be really messy though [04:16] Yeah, that's what I was thinking. [04:16] I say we have at most five days to upload this thing [04:17] We also have Andrew waiting on us to upload stuff to LXQt while DebConf is happening. [04:17] So... which one takes priority? [04:18] Calamares [04:18] OK. [04:18] See if you can enlist some help from Dan [04:19] Think about it like this... [04:19] Debian doesn't freeze until January. 22.04.1 releases in early August. What's the bigger priority? [04:19] Yeah, makes good sense to me. [04:19] * arraybolt3[m] clones calamares-packaging [04:19] We have minimum 7 days before the initial ISOs are spun [04:20] arraybolt3 @arraybolt3:matrix.org: I will be much more critical on any SRU than any development upload. It's partly why I want someone else to handle stable releases, it's a lot of work. [04:21] arraybolt3 @arraybolt3:matrix.org: And you haven't even gotten to the hard part yet. [04:21] OK. I'll go slow and careful. [04:21] Please read this entire page: https://wiki.ubuntu.com/StableReleaseUpdates [04:21] Oy. OK. [04:22] You will have a much better appreciation for the stability of Ubuntu after reading that [04:32] Honestly, this will be a good exercise for you to handle, arraybolt3 . I've handled countless SRUs at this point (quassel was a good example), and doing an SRU provides great experience. [04:33] I would say you're okay to pass off future SRUs to me or Dan if they don't interest you, but yeah, please learn the process and do it at least once. That way you have an understanding for what to do when we go bug hunting [04:33] "It's wabbit season" [04:33] 👍️ [04:34] Man, it's almost midnight where I'm at, I'm not hardly understanding what I'm reading in the SRU document. [04:35] I even just got done doing a combined FFe/SRU for a late change to 22.04 for 22.04.1 for Studio (neglected omission of libreoffice-calc, weird situation). [04:35] Is there some terminology document I can refer to? [04:35] arraybolt3[m]: Same time here, how can I help? [04:35] arraybolt3[m]: What's the terminology you're stuck on? [04:35] I don't know what an SRU review round trip is. [04:36] What's the full context? [04:36] That was the first one, there were others, but I just backed way up, so... [04:36] When you don't want to fix a subsequent interim release at all [04:36] We recognise that making it a hard requirement to fix all subsequent interim releases would mandate more work, and that a team may not have the resources available to fix and verify (say) an LTS as well as a subsequent interim release that has fewer users. We wouldn't want to block a fix from landing at all, so we are not making it a hard requirement that subsequent interim releases be fixed. [04:36] However, we strongly recommend that subsequent interim releases be fixed, and it is our expectation that normally uploaders will ensure this. If you are unable to do this, then please: 1) create and mark bug tasks against the subsequent affected releases "Won't Fix"; and 2) explicitly state in the bug that you are deliberately seeking to fix a release without fixing the subsquent releases. An SRU team member may then accept your [04:36] upload at their discretion and on a case-by-case basis. If this is not done, then uploaders should expect an SRU review round trip while your intentions are clarified. [04:37] Round trip meaning, going through the entire process [04:38] To translate that sentence... "If this is not done, then uploaders should expect a delay and perhaps re-upload while your intentions are clarified." [04:38] Ah, OK. [04:38] Also, "To stage an upload, follow the usual process but additionally add a block-proposed- tag to at least one of the SRU bugs together with a comment explaining the reason for the staging." Fantastic, so what *is* the usual process? [04:38] It's further up [04:39] Edit the bug description to include things like Test Case, keeping the original description at the bottom under its own header [04:39] Then, to stage an upload, you do that same process, where you make the bug report, but you add an additional tag to it [04:40] And that bug gets ~ubuntu-sru subscribed to it. That's how they're alerted [04:40] Britney automatically blocks packages from migrating if there's a bug filed against it with the block-proposed tag [04:40] Oh, so there's two bugs, one with the issue, and then one later when you're ready to really SRU it. [04:40] Nope, one bug [04:41] You can edit your original bug description [04:41] Eickmeyer @eickmeyer:matrix.org: Got an example handy? [04:41] Sorry, my brain is lost, thank you for your help. [04:41] All good. Perhaps some sleep will help, I know I'm hitting the hay soon. Long day [04:42] arraybolt3 @arraybolt3:matrix.org: If you don't get to this by about Friday afternoon I'll be jumping in fwiw :) [04:42] The Wiki doesn't seem to even say anything about subscribing ~ubuntu-sru, it has something about ubuntu-sponsors? [04:43] I'm guessing the one team must be a subset of the other one. [04:44] Oh, the bit about staging just clicked. OK, that's good. [04:44] I guess I once was a member of ~ubuntu-sponsors. I can join again [04:44] https://launchpad.net/~tsimonq2/+participation [04:45] So the block-proposed- tag tells Britney, "Leave this in Proposed, it needs more testing"? [04:46] Simon Quigley (Developer): On it. [04:46] arraybolt3[m]: Yes [04:46] Alright, that makes sense! OK, not all hope is lost! [04:46] If you haven't already, please also read this entire page: https://wiki.ubuntu.com/ProposedMigration (less urgent) [04:46] I've linked it a few times [04:47] bug 1980901 is the combined FFe/SRU I was mentioning. [04:47] Bug 1980901 in ubuntustudio-meta (Ubuntu Jammy) "[SRU] [FFe] libreoffice-calc erroneously missing from ubuntustudio 22.04 seed" [High, Fix Committed] https://launchpad.net/bugs/1980901 [04:47] OK. (I've not read it yet, trying to keep up with everything is hard) [04:47] As you can see, it hasn't quite passed the 7-day gestation. [04:48] Nice, that's a good overview for me to refer to. [04:48] arraybolt3[m]: All good. There's a reason this takes time [04:50] Eickmeyer[m]: That's "the round trip" [04:50] tsimonq2: Indeed. [04:51] That is also a decent overview of a typical Feature Freeze exception. [04:52] s/overview/example [04:55] If the reported autopkgtest regression is not a real regression or not a regression caused by the proposed update (but instead broken by some other dependency), the analysis of this has to be documented for the SRU team. The generally recommended way is commenting on one of the SRU bugs for the upload. Once the rationale is submitted and approved/validated by an SRU member, the SRU team will add a badtest or reset-test hint for [04:55] the broken package and release the update as per usual procedures (once validation and aging is complete). Alternatively, the uploader/verifier can modify the hints and provide an MP in the bug along with the rationale. Useful input here can be re-running the failing test against only the release/updates pocket, as documented in the ProposedMigration wiki page. [04:55] What is an "MP"? [04:56] Merge Proposal, much like a Pull Request, but in Bazaar-speak, which is how versioning used to be handled in Ubuntu. [04:57] OK. [04:57] Some components, such as Ubiquity and ubuntu-cdimage, are still handled that way. [04:58] * Eickmeyer[m] needs to head to bed before his dog goes nuts wondering why he isn't in bed yet. [05:06] OK, I digested the SRU page, ProposedMigration will have to wait until my head clears. But I'm halfway there! [05:09] Sweet! [06:28] [telegram] ack (re @lubuntu_bot: (irc) Dan Simmons @teward001 arraybolt3 guiverc Rober Leo K @lynorian @The_LoudSpeaker - please read https://lists.ubuntu.com/archives/lubuntu-devel/2022-July/001930.html) [07:03] [telegram] Done (re @lubuntu_bot: (irc) Dan Simmons @teward001 arraybolt3 guiverc Rober Leo K @lynorian @The_LoudSpeaker - please read https://lists.ubuntu.com/archives/lubuntu-devel/2022-July/001930.html) [10:14] "Dan Simmons @teward001 arraybolt..." <- /me has doodled [12:50] [telegram] Ack. (re @lubuntu_bot: (irc) Dan Simmons @teward001 arraybolt3 guiverc Rober Leo K @lynorian @The_LoudSpeaker - please read https://lists.ubuntu.com/archives/lubuntu-devel/2022-July/001930.html) [13:04] [telegram] Is lxqt 1.1 working on debian? In 32 bits it gives me a dependency error. [13:14] [telegram] https://matterbridge.lubuntu.me/e2965334/image_2022_07_21_15_14_52.png [15:55] Current candidate is Thurs at 4 PM UTC-5 [15:56] Rober: Did you plan on voting on the Doodle poll? Ditto with Raman [15:57] tsimonq2: That will actually work for me better than I thought initially. [15:59] [telegram] i look at it now, thanks (re @lubuntu_bot: (irc) Rober: Did you plan on voting on the Doodle poll? Ditto with Raman) [16:05] [telegram] Done (re @lubuntu_bot: (irc) Rober: Did you plan on voting on the Doodle poll? Ditto with Raman) [16:19] Thank you! [16:21] guiverc: I'm ready to decide on 4 PM UTC-5 Thursday which looks like the earlier morning your time. For Raman it's like 3 in the morning. We can always take your pastes beforehand. Is it okay if we decide on that? [16:22] And we can even have our first standup today. [16:22] Would it be horrible if I wanted to ask that we delay it until next week to start? Things have been going crazy on my end and so having the added stress of an impromptu standup would be a bit much. [16:23] It's always pretty lax either way, unless there's questions [16:23] OK, that's good. [16:23] If you can't participate this week it's cool :) or just give me a Markdown-formatted bullet point list of what you've done over the last week [16:24] I can paste it in for you [16:24] I think I can participate. [16:24] (Sorry if I'm a bit jumpy today...) [16:25] * arraybolt3[m] gets breakfast and then preps for standup and Calamares SRU [16:25] You're all good. I'm about to be afk to run a quick errand then probably working on EMR until that time [16:25] After the standup I can catch you up with sponsorship requests [16:27] https://github.com/lxqt/lxqt/discussions/2281 [18:22] Simon Quigley (Developer): Quick question in relation to the copyright file - There are a bunch of files in the CI directory of the GitHub repo for Calamares, are those supposed to be left out of the copyright file? [18:22] (I think I'm supposed to add them.) [18:23] arraybolt3[m]: Well, let me ask you this. Is it code that builds something in some context? [18:23] Source, not already built [18:24] It is source code, do you mean, does it do building, or is it built into something? [18:24] The latter, mostly [18:25] It's used as a source file by the CI [18:25] It's all .py and .sh files, except for one .c file that consists of nothing but a comment. [18:25] Someone had to write that source file [18:25] Right, but does it end up in the packaging? [18:25] If it never ends up part of Ubuntu, is there any reason to include it in the copyright file? [18:25] The packaging must document all of the source code in copyright, so you tell me :) [18:26] arraybolt3[m]: Well, it ends up in the source package [18:26] Ah. OK, that makes sense. [18:26] (And I didn't realize it ended up in the source package.) [18:26] Any user can enable a line in their apt sources config file and download the source code [18:26] For any package [18:26] OK, then I guess a lot of the work in the Calamares SRU is going to be wrangling the 700+ times that "Copyright" showed up between Calamares 3.2.41 and Calamares 3.2.60. [18:27] 753 to be exact. [18:28] As long as you're using git diff and not grepping individual changelogs you may be able to keep your sanity. [18:28] Yep, I'm using git diff. [18:28] https://github.com/calamares/calamares/compare/v3.2.41...v3.2.60.diff [18:29] "He's learning" 👏🤣 [18:29] It looks like a lot of it is UI elements. [18:29] arraybolt3[m]: Yeah, probably [18:31] Eat that elephant one bite at a time. [18:31] I know I'm not one to usually recommend such a thing, but if Featherpad doesn't have diff collapsing yet, paste that thing in Kate [18:32] You click an arrow on the left side and it'll collapse entire files for you so you know they're reviewed [18:32] Not a bad idea. Probably a lot better than doing it in Chrome. [18:32] * tsimonq2 would wget the file [18:32] Open in Kate [18:32] (Yes, I installed Chrome on my developer laptop. I know...) [18:33] I mean, the alternative is copy/pasting it :P [18:33] So :P [18:33] I do that for smaller diffs... [18:34] Holy cow. The diff is over 18 MB. [18:34] HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA [18:35] Okay okay so in this case... just clone the upstream Git repo locally and do the git diff, piping it to a file. Exclude all those stupid translation files :P [18:36] I like this idea! [18:36] (That's the diff size. Translation files aren't stupid, let me clarify. But most of that diff is probably translations.) [18:36] * arraybolt3[m] made the... mistake? of installing stock Ubuntu 22.04 on my laptop and now I've got GEdit to work with, which turns out to be worse than Chrome for this task [18:37] (Oh wait, there we go, figured out how to make it work... I think?) [18:38] Okay so your syntax is going to look roughly like this: `git diff TAG1 TAG2 !(translations) > long.diff` [18:38] OK, that makes sense. [18:38] Give or take depending on personal preference [18:39] You have to think... that's a years worth of translations updates to many many strings in 40+ languages [18:39] Ofc it's going to be 18 MB :P [18:39] Even if the translations haven't changed, the strings have [18:42] Rober: Not sure if you have programming experience or would like to learn as a little side project, but essentially we need a tool that will grab all of the git diffs from various upstream projects like above and review/import it into our own packaging [18:43] Imagine the kind of impact you could have if all of that information and links to all of those websites were put in one place, where you could then instruct contributors on how to translate in their free time. Promote it in the release notes and such [18:44] If you want me to handle the technical side, I can, just let me know. If you have experience or would have the time and willingness to learn, I could teach you [18:44] [telegram] @Roberalz ^ :) [18:46] @lynorian @teward001: Where did we leave off a few years back with translations for the Lubuntu Manual? [18:46] And how can we streamline that process if possible? [18:48] Simon Quigley (Developer): Well, sadly, excluding the translations is going to be hard. I can't see how to make git diff exclude just the lang directory, and the way they names the files with translations is going to be hard to exclude them without also excluding things that I need. [18:48] Time to eat the elephant. [18:49] arraybolt3[m]: Difficult or impossible? [18:49] Probably impossible. [18:49] calamares_as.ts calamares_en_GB.ts calamares_gu.ts calamares_kn.ts calamares_pt_BR.ts calamares_tg.ts kb_tg.ts... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/beb1fee74c92a32b06b1ef3914c15c0b88e9ff3f) [18:50] Also, the files begin with valid copyright headers I believe, so excluding them all could mean missing important data. [18:50] [telegram] My programming knowledge is very rusty. I haven't done anything for years. I think I could try something but I would need to understand how git diffs work first xD (re @lubuntu_bot: (irc) Rober: Not sure if you have programming experience or would like to learn as a little side project, but essentially we need a tool that will grab all of the git diffs from various upstream projects like above and review/import it into o [18:50] arraybolt3[m]: Wrong. https://stackoverflow.com/questions/10415100/exclude-file-from-git-diff?answertab=trending#tab-top [18:51] In case you want to enhance your Google-fu, this was my entire search: git diff exclude files which match pattern [18:51] First result :P [18:51] Bah, I was using my man-fu and ignoring Google entirely. [18:52] (Bah as in "Why didn't I think of that?") [18:52] Rober: That's okay, once we get past Feature Freeze we can really spend time on a lot of this stuff [18:54] [telegram] I meant to program now under that reference. :p (re @lubuntu_bot: (irc) In case you want to enhance your Google-fu, this was my entire search: git diff exclude files which match pattern) [18:55] [telegram] I would suggest spending some time playing with Python. It's my go-to language for this sort of thing. Easy to understand and very readable (re @Roberalz: I meant to program now under that reference. :p) [18:55] [telegram] And, when you're playing with something small there, you can also introduce Git into the mix [18:56] [telegram] Whenever you're ready I'm happy to link you to resources (which are very likely available in Spanish ;)) or walk you through [19:02] arraybolt3 @arraybolt3:matrix.org: Lmk what's going on with your stuff too :) [19:02] Beautiful day. Opting to take the dog for a walk [19:02] [telegram] I'll look into learning python then, while also studying the lpic2 certification :) (re @tsimonq2: Whenever you're ready I'm happy to link you to resources (which are very likely available in Spanish ;)) or walk you through) [19:02] Simon Quigley (Developer): Thanks! So far I've started to get through the copyright file, and I discovered a gedit bug! [19:03] (Load an ~18 MB file into gedit, then fiddle with the search just right and you can get the window to go black!) [19:04] [telegram] Is a feature :/ (re @lubuntu_bot: (irc) (Load an ~18 MB file into gedit, then fiddle with the search just right and you can get the window to go black!)) [19:04] No. Not possible. No one wants their screen to go black. [19:04] (Is it really a feature???) [19:05] (I was trying to be funny...) [19:06] [telegram] Hahahah (re @lubuntu_bot: (irc) (I was trying to be funny...)) [19:06] [telegram] Maybe a bug because of the file size? [19:06] I'd guess so. I was able to fix it by changing my theme to Cobalt, so I can still see what I'm doing. [19:07] [telegram] Mmmmm [19:07] [telegram] https://askubuntu.com/questions/1307503/gedit-background-becomes-black-when-i-open-a-very-large-file [19:10] @Roberalz: Solution! https://askubuntu.com/questions/1307503/gedit-background-becomes-black-when-i-open-a-very-large-file/1419834#1419834 [19:12] arraybolt3[m]: Is it just because it changes color? Well done!!!! [19:13] [telegram] The same file works in featherpad? [19:14] I don't know, I could check later. It might work in FeatherPad since FeatherPad is Qt, and the bug in gedit is in GTK I believe. [19:22] Oh nice, Ctrl+W is Find in Nano and Close File in gedit. \o/ 🤦‍♂️ === Noumeno is now known as Roberalz [19:35] [telegram] Let me know how I can help :) (re @Roberalz: I'll look into learning python then, while also studying the lpic2 certification :)) [19:44] Simon Quigley (Developer): Any special procedure for when the copyright owner of a file is given as a URL? The copyright owner of one file in Calamares is literally given as "https://www.onlinewebfonts.com/fonts". [19:46] Digging around in the website reveals the "company name" to be "Font All Free". [19:46] You can use website metadata [19:46] The contact us link doesn't do anything. [19:47] tsimonq2: What's that? [19:47] arraybolt3[m]: Website author and title [19:47]