Eickmeyer[m] | Breaking stuff, one commit at a time. | 00:51 |
---|---|---|
arraybolt3[m] | Eickmeyer: Oh dear, what's wrong? | 00:53 |
Eickmeyer[m] | arraybolt3[m]: Nothing, I was making fun of you. Tangentally related, did you ever file a bug about the Ubuntu Studio Calamares lack-of-swap-file bug? | 00:54 |
arraybolt3[m] | Eickmeyer[m]: I don't remember. :P | 00:54 |
* arraybolt3[m] finds out | 00:55 | |
Eickmeyer[m] | No worries. I found the solution. | 00:55 |
Eickmeyer[m] | Still can't do crap about the autologin issue yet. | 00:55 |
arraybolt3[m] | Yeah, looks like I never did file it. | 00:55 |
Eickmeyer[m] | I'll have to SRU it. Lunar can use the fix, too late for Kinetic since it would require a respin (fat chance) and Jammy would get it for 22.04.2. | 00:56 |
arraybolt3[m] | Eickmeyer[m]: FWIW everything worked right until I did verbatim something Simon told me to do and it failed :P | 00:56 |
Eickmeyer[m] | arraybolt3[m]: #SimonsFault | 00:56 |
arraybolt3[m] | lol | 00:57 |
arraybolt3[m] | Total off-topic, but I found out about r/SuggestALaptop earlier. Finding a system that works for people is pretty fun. | 00:57 |
arraybolt3[m] | Still haven't found a good spot to advertise a KFocus, but maybe someone will come on with a decent budget looking for a Linux system. One can dream, right? | 00:58 |
Eickmeyer[m] | I'm going to be bringing both my Kfocus systems to Summit. | 00:58 |
arraybolt3[m] | Speaking of KFocus, quite some time ago I left my laptop upside-down overnight, thinking that would be perfectly fine. (I was originally leaving it upside-down during large compile jobs.) After that one night, every time the screen comes on after having been black for a long time, I have this very visible white haze around the outer edge that takes around an hour or two to fade away. It doesn't impair my usage of the system at | 00:59 |
arraybolt3[m] | all, but I am wondering what's up with that and if maybe I accidentally messed up the screen. | 00:59 |
Eickmeyer[m] | arraybolt3[m]: Very possibly. Those things aren't made to run upside-down. | 01:00 |
arraybolt3[m] | :( Didn't know that, my other systems don't have any problem being upside down. Oh well. At any rate, it's still working fantastic. | 01:00 |
Eickmeyer[m] | Awesome. Do yourself a favor. Go on Amazon, get yourself a cheap cooling riser. | 01:01 |
arraybolt3[m] | Not a bad idea. | 01:01 |
arraybolt3[m] | (And come to think of it, I actually don't leave my systems upside-down for overnight, I leave them on their side usually, though I've only been leaving the KFocus upright like it should be, so maybe it's more like I should have been paying more attention. Hey, you live and learn. Very happy that the screen still works at all, and works this good.) | 01:02 |
Eickmeyer[m] | The XE is pretty awesome, tbh. Great little systems. | 01:03 |
arraybolt3 | Agreed. | 01:03 |
Eickmeyer[m] | I'll be using mine for my presentation in Prague. | 01:03 |
tsimonq2 | <arraybolt3[m]> "FWIW everything worked right..." <- weak sauce 💪 😆 | 01:26 |
tsimonq2 | Okay, no, seriously... | 01:27 |
tsimonq2 | Looking | 01:27 |
lubot | [telegram] <teward001> *obtains coffee then prepares for a round of evil* | 13:12 |
* kc2bez[m] energizes his personal chaos shield. | 13:13 | |
tsimonq2 | Looks like my packages were accepted and Lunar is now bootstrapped | 15:41 |
tsimonq2 | Autosync will be turned back on, probably shortly | 15:41 |
kc2bez[m] | There has been some action in the Debian LXQt team so we will need to watch out for that. | 15:45 |
arraybolt3 | tsimonq2: What all happened with that package last night? | 16:21 |
arraybolt3 | The lubuntu-meta one? | 16:21 |
=== arraybolt3_ is now known as arraybolt3 | ||
=== arraybolt3_ is now known as arraybolt3 | ||
tsimonq2 | <arraybolt3> "Simon Quigley: What all happened..." <- ENOTATCOMPUTER | 17:41 |
tsimonq2 | <arraybolt3[m]> "Simon Quigley: ^ diff containing..." <- Try this again within a Lunar (s)chroot(/LXD container) - all of the essential packages have been accepted | 21:11 |
arraybolt3[m] | 👍️ Will do soon! | 21:12 |
tsimonq2 | Thanks! | 21:13 |
* tsimonq2 sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/26324a39fe69c5bb704427605f54d09516aad29c | 21:14 | |
tsimonq2 | I used the Git copy, that diff is from https://launchpad.net/ubuntu/lunar/+queue?queue_state=1&queue_text= | 21:15 |
arraybolt3[m] | Building the Lunar schroot now. | 21:15 |
Eickmeyer[m] | That's a weird diff. | 21:16 |
arraybolt3[m] | Oh and I still forgot to sync with the archive in all my Lunar work. 🤦 | 21:16 |
arraybolt3[m] | OK so that will need done too. | 21:16 |
arraybolt3[m] | Nothing git rebase -i can't handle. | 21:18 |
arraybolt3[m] | Simon Quigley: Exact same error as before, on Lunar. | 21:19 |
arraybolt3[m] | The parentheses seem to still be confusing it. | 21:20 |
tsimonq2 | arraybolt3[m]: Upgrade to -proposed. The only time I'll EVER say that for a development cycle, but I know what's gone in, you'll be cool | 21:20 |
* arraybolt3[m] tries some apt-fu inside the schroot to do that | 21:21 | |
tsimonq2 | echo "deb http://us.archive.ubuntu.com/ubuntu lunar-proposed main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list && sudo apt update && sudo apt -y full-upgrade | 21:22 |
arraybolt3[m] | Simon Quigley: Enabling -proposed did nothing. "apt update" tells me there's nothing to update. | 21:23 |
arraybolt3[m] | And yes, it does access the -proposed archive during the update process. | 21:23 |
tsimonq2 | Here, let me just try messing around with this on my end; I have Lunar running on bare metal :P | 21:23 |
tsimonq2 | I don't know what the root problem would be here | 21:24 |
arraybolt3[m] | I think we just have syntax wrong, did you check my diff? | 21:24 |
tsimonq2 | Yeah, I'll check again though :) | 21:24 |
tsimonq2 | <arraybolt3[m]> "Oh and I still forgot to sync..." <- once CI is set up we really should script this heh | 21:24 |
arraybolt3[m] | Anyway, while you're doing that, I'll sync with the archive and try to worm that into the Git history hopefully without fouling up all of creation. | 21:25 |
tsimonq2 | just no force pushes unless you're 100% sure in what you're doing ;) | 21:25 |
arraybolt3[m] | Eh, I've not even pushed anything to Git yet so we're good. | 21:26 |
arraybolt3[m] | (Actually I did at one point way prematurely and then deleted it before anyone else (should have) used it.) | 21:26 |
tsimonq2 | Hey, as long as you're honest about your mistakes, I'm not going to yell :) | 21:28 |
arraybolt3[m] | Feels like Git is starting to get a bit easier. Still brain-bending but not as bad as before. | 21:31 |
tsimonq2 | It's a lot to take in, but once you have the ropes down, it's hard to live a developer life without it :) | 21:31 |
tsimonq2 | Always happy to help if you aren't understanding something | 21:31 |
arraybolt3[m] | Simon Quigley: Alright, scary question, but will `rm *` delete all hidden files in a directory too? I want to delete all the visible ones so I can just full-force clobber the current branch I'm on with the contents of the archive, but I don't want to accidentally nuke the .git folder either. (Caution for spectators - this command is destructive and very dangerous, don't use it unless you know what you're doing, which I don't, thus | 21:34 |
arraybolt3[m] | why I'm asking Simon.) | 21:34 |
arraybolt3[m] | I mean I could just make a copy and then try it but... | 21:34 |
arraybolt3[m] | Actually I made a backup and then tried it, worked as intended. | 21:35 |
tsimonq2 | Nope, the wildcard only matches non-hidden files, at least in my experience. If you're looking to remove hidden files, while you *could* use something like `.*`, I would be very careful about what files are in your present and parent directory. `.*` tends to match `cwd` and `../` - at least in my usage | 21:35 |
arraybolt3[m] | shudder that sounds about as bad as... what is the nickname for that command? Let's just call it Halt and Catch Fire to All Data. | 21:36 |
tsimonq2 | To be completely safe, if I need to clear an orig source from a packaging repo, I'll `rm -rf !(debian) && ls -lah && rm .foo .bar .baz` (explicitly) | 21:36 |
tsimonq2 | hah | 21:36 |
arraybolt3[m] | Simon Quigley: Alright, I have one more question (hopefully last one for now). In the archive sync, I see there was one change to Jammy that was made as well, before it switched to Kinetic. However pull-lp-source, obviously, doesn't return a Git repo, meaning that the ubuntu/jammy branch is behind and I have no way of knowing exactly what changed so that I can move just the Jammy changes over. Thoughts? Do we leave ubuntu/jammy | 21:40 |
arraybolt3[m] | forev... *lightbulb moment* nevermind, carry on | 21:40 |
arraybolt3[m] | `pull-lp-source lubuntu-meta jammy` | 21:40 |
tsimonq2 | https://code.launchpad.net/ubuntu/+source/lubuntu-meta | 21:41 |
arraybolt3[m] | Oh. | 21:41 |
arraybolt3[m] | OK nevermind I'll just use that instead. | 21:41 |
arraybolt3[m] | Shoot. I tried to do a git fetch from that repo and now have an entire slew of tags that I didn't have before that I can't get out easily. | 21:46 |
arraybolt3[m] | I mean I guess I don't have to push tags so it's not really a big deal but :( | 21:48 |
tsimonq2 | 1) You can `git fetch` specific branches from remotes, sorry, should have told you that earlier :/ | 21:48 |
tsimonq2 | 2) You can delete local tag references | 21:48 |
arraybolt3[m] | Eh, it's OK, I wasn't making or pushing any tags anyway so no harm done. | 21:51 |
tsimonq2 | No worries :) | 21:51 |
arraybolt3[m] | And... whew, got the Jammy part updated! | 21:52 |
tsimonq2 | Very nice! | 21:52 |
arraybolt3[m] | I should be just a few cherry-picks away now. | 21:52 |
arraybolt3[m] | Well Jammy and Kinetic were easy enough... and now because I did Lunar without syncing with the archive first, I have to redo the whole thing if I want to be sure I did it right akjnfi7yrtidugh9soe487tyzuyrghif | 22:01 |
arraybolt3[m] | On the bright side, I just moved all my old work to a different branch, reset ubuntu/lunar to the beginning, and now can redo it easily enough with git cherry-pick and the update script. | 22:04 |
arraybolt3[m] | (If my reporting is getting annoying, feel free to tell me, I just figure since I'm in training this is a good idea so someone can give me a quick redirection if I start flying toward a brick wall.) | 22:04 |
tsimonq2 | <arraybolt3[m]> "(If my reporting is getting..." <- Don't take me leaving you on read as a sign it's not important - I have a lot of moving parts and every once in a while need a reminder :) | 22:13 |
tsimonq2 | (I was just signing some documents) | 22:13 |
arraybolt3[m] | Ah, it wasn't that. I just thought maybe seeing tons of reports might be getting annoying. I don't need or expect you to always answer or even see everything I type. | 22:14 |
arraybolt3[m] | Lovely. So now that I'm doing it right, I need to use a Kinetic VM or similar. | 22:17 |
arraybolt3[m] | `[info] Initialising lubuntu-* package lists update... | 22:17 |
arraybolt3[m] | /usr/bin/germinate-update-metapackage: Installed debootstrap is older than in the previous version! (1.0.126+nmu1ubuntu0.1 < 1.0.126+nmu1ubuntu1)` | 22:17 |
tsimonq2 | HAHAHAHAHAHA | 22:17 |
tsimonq2 | I love that | 22:18 |
arraybolt3[m] | Me, not so much so! | 22:18 |
tsimonq2 | Well, it's cached somewhere | 22:18 |
tsimonq2 | `grep -R "1.0.126+nmu1ubuntu0.1"` (you may have to escape some special characters | 22:18 |
arraybolt3[m] | No that's the debootstrap I have installed I think. | 22:19 |
arraybolt3[m] | Yep. | 22:19 |
tsimonq2 | er then do the `ubuntu1` version with grep :) | 22:19 |
arraybolt3[m] | (I'm on Jammy.) | 22:19 |
arraybolt3[m] | Simon Quigley: It's in debootstrap-version. | 22:20 |
arraybolt3[m] | Which I think is as it should be, though maybe I need to update it to Lunar's version, in which case I need a Lunar VM. | 22:20 |
arraybolt3[m] | (Does the update script automatically update that file too?) | 22:21 |
tsimonq2 | <arraybolt3[m]> "(Does the update script automati..." <- Yeah, it does | 22:28 |
arraybolt3[m] | K, then Lunar VM it is. | 22:28 |
tsimonq2 | Trying this locally myself to see what I can come up with. Sec | 22:31 |
tsimonq2 | > <@arraybolt3:matrix.org> ```... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/98c4e2b9cb49c843a736e0e13fa726de5eaa0123>) | 22:35 |
tsimonq2 | Did you run ./update before building the package with `debuild`? | 22:35 |
arraybolt3[m] | After making the change? No. | 22:35 |
arraybolt3[m] | Like, I ran update, I did the work, I made the change, then tried sbuild. I didn't run update a second time. | 22:35 |
tsimonq2 | Ahhhhhhhh, bingo | 22:36 |
tsimonq2 | You run `update` every time you update `update.cfg` | 22:36 |
tsimonq2 | Let me make sure this completely works locally before I jump the gun, then I'll walk you through :) | 22:36 |
arraybolt3[m] | Simon Quigley: I didn't edit update.cfg though, I edited the seed files because I thought you said to do that. | 22:37 |
tsimonq2 | oHHHHHHHHHH | 22:37 |
tsimonq2 | okay let' | 22:37 |
tsimonq2 | * okay let's slow down for just a quick sec | 22:38 |
arraybolt3[m] | Meanwhile I'm going to accidentally enable -proposed whilst trying to upgrade to Lunar in a VM. | 22:39 |
tsimonq2 | All I had to do to make this work on a lunar system was this:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/73004495ecf3a1baef0ce7a714dd4162d471bbc1>) | 22:40 |
arraybolt3[m] | Yes, all of that makes sense... but then where exactly is the file where I surround "xfonts-efont-unicode" in parentheses? | 22:41 |
arraybolt3[m] | Everything built perfectly right up until I modified the seed files manually. | 22:41 |
arraybolt3[m] | Also how on earth do I upgrade to Lubuntu Lunar?... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/9ed1e59d1e2ce86c37bcc63feafe2323d9ff05cd>) | 22:42 |
tsimonq2 | Clone the seed repo in a separate dir, https://git.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu - make an MP on Launchpad, I'll accept it, then it'll magically be fixed as soon as it's merged | 22:42 |
arraybolt3[m] | (From a Kinetic VM, full updated.) | 22:42 |
tsimonq2 | > <@arraybolt3:matrix.org> Also how on earth do I upgrade to Lubuntu Lunar?... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/ed5601707c883eec29db10e4f3e95202c009dd35>) | 22:42 |
arraybolt3[m] | Simon Quigley: Oh. That's easy, OK. | 22:42 |
tsimonq2 | DO NOT RUN THIS, LOG-READING USERS: | 22:42 |
tsimonq2 | ``` | 22:42 |
tsimonq2 | sudo sed -i "s/kinetic/lunar/" /etc/apt/sources.list | 22:42 |
tsimonq2 | ``` | 22:42 |
tsimonq2 | arraybolt3[m]: All `do-release-upgrade` is, is a wrapper around running that command ^^^ and any manual workarounds required | 22:43 |
arraybolt3[m] | Oh seriously? Cool, didn't know that. | 22:43 |
tsimonq2 | Yeah :) | 22:43 |
tsimonq2 | I've always been told... a fresh install is much cleaner than an upgraded install, simply because yes, there are some occasional manual workarounds needed :/ | 22:44 |
tsimonq2 | <arraybolt3[m]> "Meanwhile I'm going to accidenta..." <- Looks like they changed this recently (good, I'm glad); to update to -proposed you should use the following: | 22:50 |
tsimonq2 | ``` | 22:50 |
tsimonq2 | $ sudo apt -t lunar-proposed full-upgrade | 22:50 |
tsimonq2 | ``` | 22:50 |
tsimonq2 | https://autopkgtest.ubuntu.com/running <- looks like that's blocking the migration of debootstrap et al. | 22:52 |
tsimonq2 | arraybolt3: I have to come back to the office tonight anyway - I'm off to the gym but if you could send me the seed MP at some point, as time allows, I'd appreciate it | 22:59 |
arraybolt3[m] | Will do hopefully, if I can figure it out. | 22:59 |
tsimonq2 | Happy to answer questions, let me know :) have fun! | 23:00 |
kc2bez[m] | <tsimonq2> "All `do-release-upgrade` is..." <- At this point in the cycle there isn't much going on so this is pretty safe really. | 23:11 |
kc2bez[m] | The substitution is safe is what I was implying. | 23:12 |
kc2bez[m] | Personally I copy my current development VM and then run the substitution magic early on. | 23:14 |
kc2bez[m] | That way I can fall back to my old VM if I need it and I can have it for a SRU or something. | 23:14 |
* arraybolt3[m] wishes I had a development machine to clone | 23:15 | |
arraybolt3[m] | I just spun up a new machine just now, since I usually just do all development work straight on my laptop. | 23:15 |
kc2bez[m] | I try to not pollute my host machine with development builds. | 23:17 |
kc2bez[m] | A LXD container works nicely instead of a VM if you want to keep things light and minimal. | 23:18 |
arraybolt3[m] | I use sbuild for everything so I figured that would keep me mostly clean. | 23:21 |
arraybolt3[m] | Everything except PPA builds that is. | 23:22 |
arraybolt3[m] | But anyway, I'll just use a VM for now. I should learn LXD at some point but it was a nightmare the first time I played with it so I've not used it in a while. | 23:23 |
arraybolt3[m] | (That was back with Ubuntu 16.04 and 20.04.) | 23:23 |
kc2bez[m] | The docs are much better now. | 23:24 |
arraybolt3[m] | And I'm not using an official Ubuntu derivative. | 23:25 |
arraybolt3[m] | And I know to not find info from random blogs on the Net. | 23:25 |
arraybolt3[m] | s/official/unofficial/ | 23:25 |
arraybolt3[m] | (Wow there's a typo for you... not using an official Ubuntu derivative?) | 23:25 |
kc2bez[m] | Anyway, having all my build stuff in my VM keeps all the git clone, pull-lp-source etc. contained away from my normal stuff along with built packages. To boot they get done on the same release that I am building for. | 23:27 |
arraybolt3[m] | Nice. | 23:28 |
arraybolt3[m] | My usual stuff is building on bare metal and then testing on a VM, and I have a ~/Projects/ubuntu dir that holds all my packaging work. | 23:28 |
arraybolt3[m] | But using a dedicated VM sounds a lot smarter. | 23:28 |
kc2bez[m] | It works well for me. You will find your groove too. | 23:30 |
arraybolt3[m] | Mine has been working for me right up until this moment 🥴 | 23:30 |
kc2bez[m] | That's the way it always goes. | 23:31 |
kc2bez[m] | XD | 23:31 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!