[00:55] <tsimonq2> Hey arraybolt3 look at this...... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/01e19f5935d09fe2ffcdfcc90c5fe1588b08eb77>)
[01:15] <tsimonq2> https://git.lubuntu.me/Lubuntu/lubuntu-breeze-config ... I feel bad I didn't even know this existed ugh.
 That worked in old versions of lxqt, but it doesn't work anymore. (re @lubuntu_bot: (irc) <tsimonq2> https://git.lubuntu.me/Lubuntu/lubuntu-breeze-config ... I feel bad I didn't even know this existed ugh.)
[01:37]  * tsimonq2 sent a code block: https://libera.ems.host/_matrix/media/v3/download/libera.chat/350931083d8eed2ab1533432c2cf8eb9885ca477
 "[telegram] <Roberalz> That..." <- Oh yeah?
[02:47] <arraybolt3[m]> > <@tsimonq2:linuxdelta.com> Hey arraybolt3 look at this...... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/6e1038336dc542a5710fb664db398c9ebe1f0aaf>)
[02:47] <tsimonq2> Yep :) at least for liblxqt
[02:48] <arraybolt3[m]> (Sorry to have been gone for a while, I yet again got pulled away.)
[02:48] <tsimonq2> No worries
[02:52] <arraybolt3[m]> Ok, so I need to finish setting up the dev env in my VM, then resume work.
[03:10] <tsimonq2> I need to get home, I'll review stuff in the morning :)
[03:17] <arraybolt3[m]> Does anyone remember what doc says which options to set for Lintian in sbuildrc? I *think* it was `['-E', '-v', 'I', 'L', '+pedantic']` but I don't remember for sure.
[03:20] <tsimonq2> I think that's correct
[03:21] <arraybolt3[m]> Heh, I guess you are the documentation for a lot of stuff so if that looks right to you, +1.
[03:21] <tsimonq2> This is all off the top of my head. I don't have notes, only reminders :)
[03:23] <tsimonq2> I've said it before, but Ansible is just downright amazing for this sort of thing. Seriously, you can set it up to configure the system just the way you like it, install whatever packages you need, and it just does it. Written in Python on the backend, YAML or INI for all the config files
[03:23] <tsimonq2> I have it set up for my production system, which also happens to be my dev system heh :)
[03:24] <tsimonq2> Anyway...
[03:24] <arraybolt3[m]> Sounds cool. Guess that's another thing that needs to be learned.
[03:31] <tsimonq2> Get the list! the earth starts to shake
[03:32] <arraybolt3[m]> I don't think you guys want my personal "to be learned" list in the middle of The List: https://notes.lubuntu.me/huOk59_iRSaAMZDl_my8bw
[03:48] <tsimonq2> Let me know if you end up making progress anywhere... would be nice to get lubuntu-meta out of the way and at least in packaging/in the queue but it likely won't be accepted until the archive actually opens
[04:34] <arraybolt3[m]> Simon Quigley: I doubt you're up this late, but... uh... where is Lubuntu's seed? :D
[04:35] <arraybolt3[m]> nvm found it
[04:45] <arraybolt3[m]> Success! https://code.launchpad.net/~arraybolt3/ubuntu-seeds/+git/ubuntu-seeds/+merge/432472 <-- Simon Quigley
[11:32] -queuebot:#lubuntu-devel- Unapproved: accepted lubuntu-default-settings [source] (lunar-proposed) [23.04.1]
[11:32] -queuebot:#lubuntu-devel- Unapproved: accepted lubuntu-artwork [source] (lunar-proposed) [23.04.1]
[14:40] <arraybolt3[m]> `Kernel panic - not syncing - coffee levels dangerously low!`
[14:40]  * genii coredumps arraybolt3[m] to study the coffee problem
[14:41]  * arraybolt3[m] 's core splats all over the floor
[14:42] <arraybolt3[m]> Alright, while things are still peaceful, I should get some coffee and food.
[14:43] <genii> heh
[17:53] <tsimonq2> Morning!
[17:54] <arraybolt3[m]> Aloha!
 "Success! https://code.launchpad..." <- Merged
[17:55]  * arraybolt3[m] seriously considers getting a second cup of coffee to prepare for the incoming storm
[17:55] <arraybolt3[m]> Thank you kindly! Firing up Lunar VM to proceed with work.
[17:56]  * arraybolt3[m] is getting in a fight in #libera over browser choices...
[17:57] <arraybolt3[m]> Hey do we want to pick a placeholder wallpaper for Lunar for telling VMs apart like we did last time, but early in the cycle this time?
[17:58] <tsimonq2> arraybolt3[m]: I think that would be a good idea, Dan Simmons what do you think?
[18:00] <tsimonq2> arraybolt3: Is lubuntu-meta the last thing on the new-release list that you know of?
[18:00] <tsimonq2> teward: I'm interested in hearing about Drone and any CI implementation once you have the chance.
[18:00] <tsimonq2> In the meantime, we should probably start with Debian LXQt, once that's all done
[18:00] <arraybolt3[m]> Simon Quigley: I don't think so, but I think this is the heaviest part of the job most likely.
[18:01] <arraybolt3[m]> Alright, running update script.
[18:01] <tsimonq2> I'd be interested in seeing which packages still need upstreaming to Debian and where the current points of contention are. "Where are we at?"
[18:02] <arraybolt3[m]> Simon Quigley: Most of them I believe are done. libfm-qt is the doozy because of symbols. Maybe I can pass that one off on you since you'll be able to defend yourself against Andrew. He was too much for me - some stuff we deliberately did, I had no clue why, and he was grilling me on it, so... :P
[18:10] <arraybolt3[m]> Anyway once I'm done with -meta I'll get a list.
[18:10] <tsimonq2> arraybolt3[m]: Thanks; I'll work through `libfm-qt` and other items on the list once we have one :)
[18:15] <arraybolt3[m]> Thanks :)
[18:15] <arraybolt3[m]> I'll also try to work with stuff, but maybe if you can show me any tricks you use for that, that would be nice, since it looks like a major headache to me.
[18:15] <tsimonq2> No worries, we'll work through it
[18:19] <arraybolt3[m]> Alright, the x font error is fixed! \o/
[18:25] <arraybolt3[m]> Whoa what in the world? I just crashed QTerminal...
[18:25] <arraybolt3[m]> Oh wait no I didn't, it just hung for some reason.
[18:29] <tsimonq2> arraybolt3[m]: I'd be interested to see how this Qt update impacts our existing applications
[18:29] <arraybolt3[m]> Makes sense. For some reason pasting with Ctrl+Shift+V failed by hanging QTerminal for a good while and then allowing it to seemingly function normally again but without pasting anything.
[18:36] <arraybolt3[m]> Simon Quigley: Alright, I believe lubuntu-meta is done. THere's only two Lintian lines I'm worried about:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/9615907118b5a27ddd421baeae56effbff8be259>)
[18:36] <tsimonq2> > <@arraybolt3:matrix.org> Simon Quigley: Alright, I believe lubuntu-meta is done. THere's only two Lintian lines I'm worried about:... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/457020c5365339eeb2db784c50f9f76dfbf6aca3>)
[18:37] <tsimonq2> The answer to that question will give you the answer to this one
[18:37] <arraybolt3[m]> I looked this up and remember thinking that these could just be ignored. Lemme check...
[18:38] <arraybolt3[m]> "Conflicts should only be used if two packages can never be unpacked at the same time, or for some situations involving virtual packages (where a version clause is not appropriate). In particular, when moving files between packages, use Breaks plus Replaces, not Conflicts plus Replaces."
[18:38] <arraybolt3[m]> The problem is I don't know what either of those two old packages do, or if they even still exist.
[18:38] <tsimonq2> Way back in the day when we were first switching to LXQt, we offered two separate metapackages, lubuntu-gtk-desktop and lubuntu-qt-desktop
[18:39] <arraybolt3[m]> I see they's considered purely virtual according to apt-cache.
[18:40] <tsimonq2> Right, so let me fill in this piece for you: (Conflicts/Breaks)/Replaces are usually dropped after an LTS if:
[18:40] <tsimonq2>  - LTS-1 had those virtual packages
[18:40] <tsimonq2>  - LTS has the proper Breaks/Replaces, to move users onto the correct package
[18:41] <tsimonq2> As in... if 20.04 shipped with the lubuntu-qt-desktop metapackage installed by default, we want users upgrading to 22.04 to automatically be moved to lubuntu-desktop, having removed lubuntu-qt-desktop beforehand
[18:41] <tsimonq2> That's what those fields do
[18:41] <tsimonq2> So, if the upgrade path is good, if LTS -> LTS works and Kinetic -> Lunar works, you may consider dropping those lines and then re-testing Kinetic -> Lunar upgrades
[18:42] <tsimonq2> Again, the entire goal is, "we deprecated this binary package, if you try to install it it will automatically install lubuntu-desktop, and once we no longer need to account for an upgrade path where 'pre-upgrade' has the deprecated binary package, you can drop that line"
[18:42] <tsimonq2> I've never had to explain this concept to someone else, so please let me know what your questions are :)
[18:43] <arraybolt3[m]> So basically they were just a tool to make upgrades go smoothly and now that the tool has done its job we can test to make sure it really has done its job and then discard it?
[18:43] <tsimonq2> Yeah, basically
[18:43] <tsimonq2> My gut is just to drop any Breaks/Replaces lines on lubuntu-qt-desktop and lubuntu-gtk-desktop
[18:43] <arraybolt3[m]> OK that makes sense. And that's the solution I was thinking of also.
[18:44] <arraybolt3[m]> So this is one of those tricky situations involving virtual packages that the Lintian page was talking about.
[18:44] <tsimonq2> Yep ;)
[18:44] <arraybolt3[m]> OK, I'll try dropping them and see if it builds, then... how do we test if it upgrades right? PPA?
[18:45] <arraybolt3[m]> Upload to archive and see what happens?
[18:45] <arraybolt3[m]> (The latter seems easier and relatively safe at this point in the cycle.)
[18:45] <tsimonq2> Yeah, I'd throw it in a PPA, try a fresh install of Kinetic, do the aforementioned substitution dance, add the PPA, and *then* `full-upgrade`
[18:45] <arraybolt3[m]> Ah, OK.
[18:46] <arraybolt3[m]> deep breath now I have to move my GPG key into the VM
[18:46] <tsimonq2> arraybolt3[m]: I mean... no you don't ;)
[18:47] <arraybolt3[m]> Well I can move the packaging out of the VM and then sign and upload it but that's even more difficult.
[18:47] <tsimonq2> `debuild -us -uc [...]` to get the files, transfer the files to your host for signing and upload from there?
[18:47] <arraybolt3[m]> Getting files out of Boxes is much trickier than getting them in :P
[18:47] <tsimonq2> :P
[18:47] <arraybolt3[m]> I dunno though, it may be worth it so that I don't have a bunch of GPG mess everywhere.
[18:48] <tsimonq2> Oh, and in your PPA, I'd enable the proposed pocket explicitly. It's in the PPA settings, but a lot of these initial packages to bootstrap haven't migrated yet
[18:48] <arraybolt3[m]> tsimonq2: I thought it was `debuild -S -d -sa`?
[18:48] <tsimonq2> arraybolt3[m]: `-us -uc` skips signing
[18:48] <arraybolt3[m]> Oh. OK I get it.
[18:48] <arraybolt3[m]> And then I can sign after the fact how? (I know I can look this up but that would possibly take a while.)
[18:49] <tsimonq2> `debsign -k<MYKEYIDHERE> /path/to/source.changes`
[18:50] <arraybolt3[m]> Nice! Thank you!
[18:50] <tsimonq2> Of course :)
[18:50] <arraybolt3[m]> (Now I remember seeing that tool before I think :P)
[18:54] <teward> tsimonq2: I've been trying to reach you about renewing your expired car insurance
[18:55] <teward> tsimonq2: i've been a bit too busy to stab Drone into submission, but once we get Drone set up it should be trivial to define CI - except that you have the CI as a definition in the repository so Drone can see it, and then we enable it.  I've got a ton to get done today so I can't discuss it right now
[18:57] <tsimonq2> teward: WE HAVE BEEN TRYING TO REACH YOU ABOUT YOUR CAR'S EXTENDED WARRANTY
[18:57] <tsimonq2> lmao
[18:57] <tsimonq2> anyway
[18:57] <tsimonq2> teward: No worries, I'll see if I can play with it At Some Point
[18:57] <teward> tsimonq2: i don't think i've enabled it everywhere yet on Gitea.  I've got a test repo but i'm busy as shit so i'll take a peek at it later but i'm busy for today
[18:58] <tsimonq2> cool cool :)
[19:36] <arraybolt3[m]> Simon Quigley: OK so this is interesting. I removed all of the Breaks/Replaces/Provides from lubuntu-meta, sbuild'ed it, installed it, then rebooted. Somehow that has set the default wallpaper to the original kudu from Unsplash rather than the one that was picked for the final ISO.
[19:36] <arraybolt3[m]> I have no clue how on earth installing that managed to mess with lubuntu-artwork, but... it did.
[19:37] <tsimonq2> red herring - I've seen similar wallpaper-related bugs on my own system
[19:37] <arraybolt3[m]> Oh OK.
[19:38] <arraybolt3[m]> I wonder what on earth is wrong with the wallpaper? I mean the symlinks are literally now pointing to the original pictures.
[19:38] <arraybolt3[m]> So something changed them...
[19:38] <arraybolt3[m]> OK well I guess I'll finish getting a shared folder set up and then get this built and signed.
 "I wonder what on earth is..." <- My *guess* is that it's cached somewhere and the cache regeneration is racey
[19:49] <arraybolt3[m]> PPA upload complete, will test once it's finished building and publishing.
 "I wonder what on earth is..." <- Er... at least one symlink has changed, I didn't check both.
 "Er... at least one symlink has..." <- Interesting... a bug worth tracking down either way :)
[20:53] <arraybolt3[m]> Alright, back.
[21:15] <tsimonq2> Note: I have to be in bed by 8 PM or soon thereafter to get up in time for my passport appointment. Please get things to me by 6 PM. Thanks!
[21:16] <arraybolt3[m]> Prepping the VM now.
[21:16] <arraybolt3[m]> In fact I think I'm to the point where I do the upgrade and PPA-add.
[21:23] <arraybolt3[m]> Simon Quigley: Alright, everything's working! I'm going to push to Gitea directly onto the ubuntu/lunar branch if that's OK with you.
[21:24] <arraybolt3[m]> (Just dawned on me that ubuntu/lunar isn't a branch yet, so push, here we come!)
[21:25] <arraybolt3[m]> Simon Quigley: https://git.lubuntu.me/Lubuntu/lubuntu-meta/src/branch/ubuntu/lunar
[21:25] <arraybolt3[m]> Builds Lintian-clean, upgrades with zero issues.
[21:26] <arraybolt3[m]> Also I think I found the wallpaper problem - there's a Lunar update to lubuntu-artwork. I'm guessing they accidentally reverted something.
[21:27] <tsimonq2> arraybolt3[m]: This changelog message is misleading... Conflicts not Breaks :) https://git.lubuntu.me/Lubuntu/lubuntu-meta/commit/bacb1e67a749a5a0dc1fa73c6b0eb79390e5b61e
[21:27] -ubot93:#lubuntu-devel- Commit bacb1e6 in Lubuntu/lubuntu-meta "Dropped obsolete Breaks/Replaces/Provides"
[21:27] <arraybolt3[m]> :facepalm: Fixing.
[21:28] <tsimonq2> Otherwise LGTM, will update before EOD
[21:28] <tsimonq2> Pop quiz: when do you tag the final upload?
[21:28] <tsimonq2> (With Git)
[21:28] <arraybolt3[m]> Alright, finished pushing.
[21:29] <arraybolt3[m]> tsimonq2: Looks like at the very end from what I'm seeing previously in the Git repo, so my last commit should be tagged.
[21:29] <arraybolt3[m]> So at the end of preparing for an new release.
[21:29] <arraybolt3[m]> Forgot to do that.
[21:29] <tsimonq2> arraybolt3[m]: Right, but when?
[21:29] <arraybolt3[m]> Vague wording, sorry. When you make the final commit for a new release.
[21:30] <tsimonq2> The mantra I've been "raised on" is, wait to push the tag until the upload is accepted into the archive
[21:30] <arraybolt3[m]> Oh, OK, that makes sense.
[21:30] <tsimonq2> Makes it easier to iterate on if your sponsor/the queue reviewer wants changes made :)
[21:31] <arraybolt3[m]> Because there could be more changes you need to make.
[21:31] <arraybolt3[m]> So I was right, but also am premature in going to create the tag.
[21:31] <tsimonq2> I mean, you can create the tag locally, that isn't an issue
[21:31] <tsimonq2> I'd just wait to push the tag :)
[21:32] <arraybolt3[m]> And also maybe fix my mangled tag mess that I had locally earlier.
[21:32] <arraybolt3[m]> (That git fetch bit me hard, thankfully I didn't have to push the tags and so now I can just reclone the repo and have all that junk fall off.)
[21:32] <arraybolt3[m]> Which does indeed appear to have worked.
[21:33] <arraybolt3[m]> Hey I did create an ubuntu/kinetic branch - should I be tagging and pushing that too?
[21:36] <tsimonq2> arraybolt3[m]: Perfect :)
[21:37] <tsimonq2> arraybolt3[m]: Here's the most logical workflow I've been able to come up with...
[21:38] <tsimonq2> There is a point, somewhere in the Git history for all of our packages, a point at which it is completely in-sync with the archive
[21:39] <tsimonq2> Before tagging is done, you should be checking to make sure that the archive exactly matches your local copy, minus the .git folder
[21:39] <tsimonq2> I never wrote that down I don't think, so it never became policy for us all, so we've let that slide
[21:40] <tsimonq2> When you're importing from the archive, keep that in mind. Any change a human commits to the repo should be self-contained. You aren't personally making any other changes besides importing, but you want that tag history for every upload that's ever hit the archive
[21:42] <tsimonq2> I would find the "last known good point". If it's an older release, start with that branch and import uploads one-by-one. Launchpad always has copies of diffs and filterdiff is a thing, so this could (and probably should) be automated
[21:42] <tsimonq2> When you've hit the end of a release, create a new branch from the one you've just finished. Work your way up again
[21:42] <tsimonq2> Repeat until you get to $now
[21:43] <tsimonq2> That is the most correct way to do it
[21:44] <tsimonq2> As for the quickest way to do it? As long as it roughly follows that logic, get creative :)
[21:47] <arraybolt3[m]> Sounds like pretty much what I did except for the tagging. I made sure I was perfectly exactly in sync with the archive for all of the Kinetic commits.
[21:47] <arraybolt3[m]> So now I can just tag as needed and push the branch and the tags.
[21:47] <tsimonq2> Correct, except for the latest tag :)
[21:48] <arraybolt3[m]> In Kinetic?
[21:48] <tsimonq2> Did all of that make sense?
[21:48] <arraybolt3[m]> The latest tag in Lunar, yes, hold off on, but the latest in Kinetic is already said and done.
[21:48] <tsimonq2> arraybolt3[m]: If it's said and done, yeah, tag and push :)
 "I would find the "last known..." <- OK and I started from Jammy, imported what needed it, so I also need to add a Jammy tag. And I made sure that I had the archive and Git repo in perfect sync.
[21:50] <arraybolt3[m]> Alrighty, here goes!
[21:51] <tsimonq2> arraybolt3[m]: Remember the scripts I posted last night :)
[21:52] <arraybolt3[m]> Nice. I took a slightly more "sledgehammer" approach to it and made sure that all the changes from the archive were applied properly by just nuking everything locally and then copying the right part of the archive to it, then using gitk to make sure it looked sane.
[21:52] <arraybolt3[m]> But I should save those scripts somewhere for future work.
[21:55] <arraybolt3[m]> So weird. QTerminal just randomly stops letting paste functionality work out of nowhere.
[21:58] <arraybolt3[m]> Ssssssshhoooooott. I just accidentally did "git push --tags" from within the tag-mangled repo.
[21:58] <arraybolt3[m]> It doesn't look like all the garbage tags are even visible, but crud. Do I just delete them and then redo git push --tags?
[21:59] <tsimonq2> arraybolt3[m]: Nope, because that won't delete the remote copy...
[21:59] <arraybolt3[m]> Dagnabbit. This is what I get for having two repos with otherwise identical data in the same folder.
[21:59] <tsimonq2> Remember the `git push origin :master` trick? (DO NOT RUN THIS, EVER, DEAR READERS)
[21:59] <tsimonq2> Yeah that works with tags too
[22:00] <tsimonq2> And when you pushed it, git should have given you an output of what tags it pushed, yeah?
[22:00] <arraybolt3[m]> Yes.
[22:00] <tsimonq2> Alright, give me a second to find some info on querying remote tags from the CLI to see if you have any weirdness going on
[22:01] <tsimonq2> https://stackoverflow.com/questions/25984310/how-to-see-remote-tags
[22:01] <arraybolt3[m]> All that went wrong is when I did a "git fetch upstream" to get the necessary info from Launchpad, it pulled in a WHOPPING LOAD of tags from Launchpad. Now they all just got pushed to Gitea. Tons of "imported" and "accepted" things.
[22:02] <tsimonq2> Nice job ;) don't worry, totally fixable
[22:02] <arraybolt3[m]> The output of "git ls-remote --tags origin"
[22:03] <arraybolt3[m]> Hold on, it was too big to paste into Matrix.
[22:03] <arraybolt3[m]> https://termbin.com/hzv6
[22:04] <tsimonq2> First things first, the import tags will be easy
[22:04] <tsimonq2> https://stackoverflow.com/questions/45818817/delete-multiple-git-remote-tags-and-push-once
[22:05] <tsimonq2> We don't have any import/ tags, I'd use a variation of that to get rid of all of them in GiTea
[22:05] <arraybolt3[m]> So `git push -d origin $(git tag -l "import/*")`?
[22:05] <arraybolt3[m]> (DANGEROUS COMMAND ABOVE FOR BACKLOG READERS)
[22:05] <tsimonq2> If you want practice beforehand, you can always make a copy of the directory, add the copy path as a remote to your original Git repo, and test the deletions there
[22:06] <tsimonq2> arraybolt3[m]: That seems about right, go for it
[22:06] <arraybolt3[m]> That's smart. I can also just run the git tag command to see what it's going to try and remove.
[22:07] <arraybolt3[m]> Alright, looks good, command is running.
[22:07] <tsimonq2> I have to use that trick for $dayjob :P
[22:07] <arraybolt3[m]> YAY it worked.
[22:07] <tsimonq2> NICE
[22:08] <arraybolt3[m]> So now rinse and repeat with "applied/", right? After making sure we don't use that prefix?
[22:08] <arraybolt3[m]> (I don't see that prefix in use in gitk.)
[22:08] <tsimonq2> Yep :)
[22:09] <tsimonq2> Also, check the ubuntu/ tags. You don't want to remove those tags if they're pointing to the right commits
[22:09] <arraybolt3[m]> I think every ubuntu/ tag is correct.
[22:09] <tsimonq2> You do want to remove them if they're pointing to Launchpad refs
[22:09] <arraybolt3[m]> I will double-check to see if they need to be removed.
[22:10] <arraybolt3[m]> "applied/*" has now been nuked, *whew!*. Thank you for saving me from that and for not tearing me to pieces for botching like that on production.
 "I think that would be a good..." <- I concur, excellent idea.
[22:11] <tsimonq2> arraybolt3[m]: Like I said before, if you're honest about your mistakes I have zero issue helping you fix them :)
[22:12] <arraybolt3[m]> Thank you. :) I have no problem with being honest with a mistake. Better to make the whole team work than to make ones' self look good (not to mention the fallout if it was discovered later and the fact that stuff like that is pretty difficult to hide...).
[22:12] <tsimonq2> Agreed :)
[22:13] <tsimonq2> Speaking of agreeing, I think we should definitely get that wallpaper stuff on the list ;)
 "I wonder what on earth is..." <- The symlinks are in 2 different packages I think. Default settings and artwork.
[22:13] <arraybolt3[m]> kc2bez[m]: When I worked on artwork I saw both symlinks in there IIRC.
[22:14] <arraybolt3[m]> And it's a lubuntu-artwork update that causes the wallpapers to go wonky.
[22:14] <arraybolt3[m]> tsimonq2: Will add 👍
[22:16] <tsimonq2> arraybolt3[m]: May be 16 year old Simon's fault :P
[22:17] <kc2bez[m]> tsimonq2: TBF I could have dove into it deeper too.
[22:17] <tsimonq2> Ideally, the symlinks would only be in the artwork package, I think
[22:17] <kc2bez[m]> I agree.
[22:17] <arraybolt3[m]> Simon Quigley: OK what is this? `daa59645570c0c7a24aec21268e7706779e6089c        refs/tags/ubuntu/20.04.3^{}`
[22:17] <arraybolt3[m]> I know that ubuntu/20.04.3 is ,and I *think* the ^ is "before", but the {} has me stumped.
[22:18] <arraybolt3[m]> Is that a tag that needs removed, or what even is it?
[22:18] <arraybolt3[m]> (It's one of only two tags that I didn't see in gitk.)
[22:18] <tsimonq2> Maybe... a pointer of some kind? Try just doing `git tag` no arguments
[22:19] <arraybolt3[m]> I don't see it in there.
[22:19] <tsimonq2> Is it a different commit ref than the one without the suffix?
[22:19] <arraybolt3[m]> What I did find out from the Launchpad tag intrusion nightmare is that we missed a tag in Focal, though.
[22:19] <arraybolt3[m]> Ooo, good question, one moment...
[22:20] <arraybolt3[m]> Simon Quigley: No. The commit SHA1's are identical.
[22:21] <tsimonq2> Perfect, so I say ignore it
[22:21] <arraybolt3[m]> (As determined by doing "git checkout ubuntu/20.04.3" then using gitk to find the commit SHA1.)
[22:21] <arraybolt3[m]> OK, that leaves only ubuntu/20.04.7, which actually has a spot it belongs, so I guess I'll get that in carefully.
[22:22] <arraybolt3[m]> deep sigh of relief All the bad tags are gone.
[22:22] <tsimonq2> Sweeeeet :)
[22:26] <arraybolt3[m]> And the one missing tag has been added. So hey, after nearly giving myself a heart attack and having to be bailed out by an expert developer, we actually fixed a minor issue! 🥴
[22:28] <arraybolt3[m]> Simon Quigley: OK, so just so I make sure I know what else I need to do, I saw you already did the Calamares desktop file, so I'm guessing you probably also finished the rest of the list while I was fighting with lubuntu-meta. Is there anything left on the list I need to do?
[22:30] <arraybolt3[m]> Like, did we already update the default seed branch in Launchpad and Gitea? ANd whatever needed done with repo-list and the setup-phab script? And the Github default branches for the mirrored repositories? (I don't think I even can do that last one.)
[22:30] <arraybolt3[m]> (I don't know if the use of setup-phab is still a thing.)
[22:32] <tsimonq2> arraybolt3[m]: Nope, it isn't
[22:32] <arraybolt3[m]> IT needs rewritten for Gitea doesn't it?
[22:32] <arraybolt3[m]> It looks to me like it goes through all the repos and makes ubuntu/RELEASE branches (in our case, ubuntu/lunar).
[22:33] <tsimonq2> Yeah :)
[22:33] <tsimonq2> arraybolt3[m]: I think that's about it, sure
[22:34] <arraybolt3[m]> K. That looks to me like the last thing I can do that needs done as far as bootstrapping, except for maybe lintian and devscripts.
[22:34] <arraybolt3[m]> I don't know how to change the default branch for the seeds if it hasn't been changed already, and I don't think I have proper access to GitHub to change branches (and I have no idea what I would be doing there and probably shouldn't have that access yet), but the creation of the ubuntu/lunar branches looks like something that's doable.
[22:36] <tsimonq2> arraybolt3[m]: Those are all done :)
[22:36] <tsimonq2> arraybolt3[m]: Do what you can and let me know what's left :)
[22:37] <kc2bez[m]> The seed branch is usually done by a release team member. If you look in phab or LP you can see it changed already.
[22:38] <arraybolt3[m]> kc2bez[m]: Makes sense. Where exactly would I look to see that change?
[22:39] <kc2bez[m]> It isn't set as default but the branch is created
[22:39] <arraybolt3[m]> Simon Quigley: lubuntu-meta has been completed. I believe it is ready for sponsoring. (You probably already knew that but just in case, I thought I should probably say it so that nothing got missed on account of me.)
[22:40] <kc2bez[m]> https://phab.lubuntu.me/source/seed/browse/lunar/
[22:41] <kc2bez[m]> You will see if you clone that it actually clones the LP repo
[22:41] <arraybolt3[m]> Ah, OK. So in LP it needs changed. So I'm guessing that means I need to make another MP.
[22:43] <arraybolt3[m]> Actually, it looks like "default branch" isn't something handled by Git AFAICT. I don't think I have access to change that, and I probably shouldn't change it in Gitea since that should be automatically changes when LP changes, right?
[22:43] <kc2bez[m]> I don't think it is a function of git, no.
[22:43] <kc2bez[m]> I've always adjusted it in the web interface.
[22:43] <arraybolt3[m]> OK.
[22:44] <kc2bez[m]> Maybe Simon Quigley knows some git-fu
[22:44] <arraybolt3[m]> Then I guess the last thing to be done that I can do is the setup-gitea script.
[22:44] <tsimonq2> refs/heads/head ?
[22:46] <tsimonq2> git symbolic-ref HEAD refs/heads/ubuntu/lunar && git push origin HEAD:HEAD  ???
[22:46] <arraybolt3[m]> https://stackoverflow.com/questions/51274430/change-from-master-to-a-new-default-branch-git That looks somewhat like the right idea to me.
[22:46] <arraybolt3[m]> Though I don't know if an MP is going to modify that since that's not a part of any git branch I don't think.
[22:47] <arraybolt3[m]> I might modify the default branch of my own repo but I don't think that will carry over. Plus the web UI sounds way easier.
[22:48] <tsimonq2> arraybolt3[m]: True, true :)
[22:48] <tsimonq2> One of these days you'll be in ~lubuntu-dev so you can Just Do It :P
[22:48] <kc2bez[m]> tsimonq2: This ^
[22:48] <arraybolt3[m]> 👍 That was my question, whether I had access to do it or not and how to do it. If I don't have access, problem solved.
[22:50] <arraybolt3[m]> OK, life calls again. I'll be back later (probably tonight) to do the setup-gitea script, and then I think everything I can do will have been done. All that I think is left is the default branch for the seeds and the Github branches for the mirrored repositories.
[22:50]  * arraybolt3[m] goes afk, thank you guys and be back soon!
[22:50] <kc2bez[m]> Take care, I have to go to.


[08:29] <boss> hi,i am new bie in ubuntu.I want to know how to install ubuntu in the client machines from the local server where internet connection is not available.I have CD rom drive only in a single machine(server).
[11:49] <booxter> Hello! I'm a Belarusian Latin translator and I would like to see Ubuntu LiveCD and installer to be Belarusian-Latin supported. What should I do to take the goal? Is there a technical possibility for doing this?
[01:05] <mpt> booxter, you want to translate the installer into Belarusian?
[01:05] <booxter> mpt, yes
[01:06] <mpt> booxter, you can do that on https://translations.launchpad.net/ubuntu
[01:07] <mpt> booxter, for example, https://translations.launchpad.net/ubuntu/gutsy/+lang/be
[01:07] <booxter> Launchpad technically doesn't support our be@latin locale...
[01:08] <booxter> so we need some kind of "manual" way of translation
[01:08] <mpt> Oh, I'm sorry, that's Belarusian Cyrillic, isn't it
[01:08] <mpt> You want Belarusian Latin
[01:08] <mpt> ok, so you need to get Belarusian Latin registered in Launchpad
[01:09] <booxter> yes, we need
[01:09] <booxter> but there is a known bug that prevents us from doing so
[01:09] <booxter> sr@Latn (Serbian Latin) also has such problem
[01:09] <cjwatson> getting the installer to support that is a lot harder
[01:09] <cjwatson> you really need to get it done upstream in Debian
[01:09] <booxter> our locale technically is a variant of "be" locale
[01:10] <cjwatson> simply having the translation there isn't enough - localechooser needs to support it too
[01:10] <mpt> oh
[01:10] <cjwatson> and it takes an enormous number of uploads of individual components to Ubuntu to add a new language, diverging each of them from Debian individually
[01:10] <cjwatson> so I prefer not to do it that way, and to ask people to get the base installer translated in Debian first
[01:12] <booxter> So should we at first translate debian installer?
[01:12] <cjwatson> right
[01:12] <booxter> are there any significant changes between vanilla installer and ubuntu one?
[01:12] <cjwatson> yes
[01:12] <cjwatson> so just translating the Debian installer won't be enough, but it's the first step
[01:13] <booxter> hm, as I know there are several "levels" of Debian translation
[01:13] <booxter> what levels are sinificant for Ubuntu, what are less?
[01:13] <booxter> And after what level can we incorporate Ubuntu version of installer to make sure we are ready?
[01:14] <cjwatson> level 1 is the only one that's a blocker here
[01:14] <cjwatson> obviously the rest don't hurt
[01:15] <mpt> booxter, I'm discussing it in #launchpad with one of the Launchpad Translations developers
[01:15] <booxter> Are other levels not used for Ubuntu version?
[01:15] <mpt> Apparently Cyrillic->Latin conversion can be done automatically for Serbian, and maybe for Belarusian too
[01:16] <mpt> but there's no schedule for implementing it yet
[01:16] <booxter> mpt, we in Belarusian community already begins to use such translation, but not fully automatically (because we use different convensions and so on)
[01:16] <cjwatson> booxter: they're used to one extent or another, but some particular packages there are less important than others and in any event it doesn't usually block switching on a language in localechooser
[01:17] <cjwatson> there's a point at which packages begin to become subject to language packs, at which point it all gets a lot easier for you
[01:17] <cjwatson> but the core installer, mostly the stuff in level 1 plus dpkg, apt, tasksel, probably a couple of others I forget right now, isn't subject to language packs because this is all before language packs get installed
[01:17] <booxter> cjwatson, we already reported a bug about Language chooser
[01:18] <cjwatson> you did? where?
[01:18] <cjwatson> I won't fix it directly in Ubuntu anyway - like I say, this really needs to be done in Debian first otherwise the maintenance burden for us to diverge every installer component from Debian is intolerable
[01:19] <cjwatson> but I'm more than happy to support the language once the basic bits are done in Debian and uploaded there
[01:22] <booxter> hm, ok, we'll do our best for Debian Installer and after level 1 will come here again:)
[01:25] <cjwatson> sounds lovely
[01:25] <booxter> ;)
[01:44] <CIA-18> ubiquity: cjwatson * r2316 ubiquity/debian/ (79 files in 2 dirs): * Update translations from Rosetta.
[02:09] <CIA-18> ubiquity: cjwatson * r2317 ubiquity/ (d-i/manifest debian/changelog):
[02:09] <CIA-18> ubiquity: * Automatic update of included source packages: choose-mirror 2.15ubuntu2,
[02:09] <CIA-18> ubiquity:  debian-installer-utils 1.48ubuntu2.
[02:22] <CIA-18> ubiquity: cjwatson * r2318 ubiquity/debian/ (changelog rules): * Disable the intro message, as Ubuntu 7.10 is approaching.
[02:38] <CIA-18> ubiquity: cjwatson * r2319 ubiquity/debian/changelog: releasing version 1.6.2
[04:23] <CIA-18> ubiquity: evand * r2320 ubiquity/ (configure configure.ac): bump to 1.6.3
[04:26] <CIA-18> ubiquity: evand * r2321 ubiquity/ (debian/changelog ubiquity/frontend/gtk_ui.py):
[04:26] <CIA-18> ubiquity: * Remember to not use the migration-assistant dbfilter when using
[04:26] <CIA-18> ubiquity:  --no-migration-assistant, again (LP: #148766).
[04:43] <CIA-18> ubiquity: evand * r2322 ubiquity/ubiquity/frontend/ (kde_ui.py noninteractive.py): Apply the previous change to the kde and noninteractive frontends.
[04:47] <mebrown> cjwatson, saw your commit for #149159 (console reboot message). is this in todays daily build?
[04:48] <cjwatson> it should be$ wget -q -O- http://cdimage.ubuntu.com/daily-live/current/gutsy-desktop-i386.manifest | grep ^casper
[04:48] <cjwatson> casper 1.109
[04:48] <cjwatson> yes
[04:48] <mebrown> thx.
[04:48] <mebrown> did you see my email about language packs?
[04:49] <mebrown> really need some help with that one, as I am not a debian/dpkg/apt expert
[04:49] <cjwatson> language-pack-* shouldn't have external dependencies
[04:49] <cjwatson> it's only a problem at all if you need language-support-* too
[04:50] <mebrown> I want a complete and good experience for our non-english-speaking customers
[04:50] <cjwatson> evand: could you help mebrown out? I have a deadline of today for UDS planning
[04:50] <evand> cjwatson: sure
[04:51] <cjwatson> germinate may be useful
[04:51] <mebrown> ok. I looked at debmirror yesterday and it didnt seem useful (no dependency tracking, afaict)
[04:51] <mebrown> I'll take a look at germinate.
[04:52] <cjwatson> debmirror does not follow dependencies
[04:54] <evand> https://wiki.ubuntu.com/SeedManagement might help with setting up a seed for germinate.
[04:54] <mebrown> thanks. reading...
[05:03] <mebrown> evand: regarding noninteractive... doesnt work
[05:03] <evand> mebrown: where does it fall over?
[05:03] <mebrown> No cut-n-paste, but it traces back:
[05:03] <mebrown> frontend/noninteractive.py, line 133 in watch_debconf_fd_helper
[05:03] <cjwatson> I would avoid trying text installs in gutsy. They aren't well enough tested.
[05:04] <mebrown>   return callback(souce, dbbconf_condition)
[05:04] <cjwatson> at least not using ubiquity
[05:04] <mebrown> file ubituqity/filteredcommand.py, line 179 in process_input
[05:04] <mebrown> file ubituqity/filteredcommand.py, line 112, process_line
[05:04] <mebrown> ubiquity/debocnffilter.py, line 236
[05:04] <mebrown> file ubiquity/components/language.py line 105
[05:05] <mebrown> file ubiquity/filteredcommand.py, line 359 in run
[05:05] <mebrown>   -> if not self.frontend.installing:
[05:05] <mebrown> AttributeError: wizard instance has no attribute 'installing'
[05:05] <mebrown> and it starts X before falling over.
[05:06] <mebrown> What I am trying to accomplish:
[05:06] <mebrown> Need to have a way to install machines that potentially dont have X support in the current gutsy image
[05:06] <cjwatson> mebrown: I understand your need, but 7.10 isn't yet ready to fill it with the live CD
[05:06] <mebrown> ok.
[05:06] <mebrown> we can respin the image, I suppose
[05:07] <mebrown> if we get a machine like this.
[05:07] <cjwatson> we should be able to fix the specific bug above though
[05:07] <mebrown> or, can probably force vesa mode
[05:07] <cjwatson> I think that's more likely to work
[05:07] <mebrown> just want to make sure I have a fallback
[05:07] <cjwatson> oh, forcing vesa should be pretty safe
[05:07] <mebrown> because we *always* get machines that come down with no X support (we install addon stuff in post)
[05:08] <mebrown> evand, did you need a lp?
[05:08] <evand> mebrown: if it's not too much trouble
[05:08] <mebrown> ok.
[05:11] <mebrown> https://bugs.launchpad.net/dell/+bug/149473
[05:11] <evand> thank you
[05:14] <evand> cjwatson: I know you're busy, so feel free to respond to this whenever you have free time.  What is the reasoning for marking bugs as invalid in a package and then adding them to a different package, rather than just switching the package?
[05:15] <mebrown> https://bugs.launchpad.net/ubuntu/+source/casper/+bug/149477
[05:16] <mebrown> I'm installing a machine now to try out germinate. Will probably have more questions in a couple hours, but it looks like this is probably what I want.
[05:18] <evand> great
[05:19] <cjwatson> evand: usually an accident
[05:19] <cjwatson> evand: note though that you can't just reassign from a package to an upstream project
[05:20] <cjwatson> so say if a bug is really a cdimage bug then it has to have a task opened on ubuntu-cdimage and the Ubuntu task rejected
[05:21] <evand> ok
[05:21] <evand> thanks
[06:19] <CIA-18> ubiquity: evand * r2323 ubiquity/ (debian/changelog ubiquity/frontend/noninteractive.py):
[06:19] <CIA-18> ubiquity: * Update noninteractive frontend to use recent changes to
[06:19] <CIA-18> ubiquity:  FilteredCommand (LP: #149473).
[07:17] <bdmurray> cjwatson: Did you see my /etc/papersize question?
[07:22] <cjwatson> bdmurray: no
[07:27] <bdmurray> I believe there was a bug in ubiquity where papersize was not being set which is now fixed but what happens to people who installed with ubiquity before it was fixed.
[07:29] <bdmurray> It is probably a small number of people and I don't know how many things look at that file either.
[07:30] <cjwatson> there was a bug, upgrades aren't handled, it should probably be release-noted
[07:30] <cjwatson> a core library looks at that file which I believe a number of desktop applications use
[07:33] <bdmurray> Okay, do we have process for release noting things?
[07:33] <cjwatson> we need to create some release notes :-)
[07:33] <cjwatson> hang on a mo
[07:34] <cjwatson> aha, GutsyGibbon/ReleaseNotes
[07:34] <cjwatson> please feel free to add to that
[07:37] <bdmurray> Okay, will do.
[07:37] <bdmurray> Thanks.
[09:44] <mebrown> is there a bug in today's daily build regarding sudo?
[09:44] <mebrown> oem install
[09:44] <evand> not that I'm aware of
[09:44] <mebrown> when I create a user at firstboot, that user cant sudo
[09:44] <evand> hrm
[09:44] <mebrown> and I cant login as root
[09:44] <mebrown> since I didnt set pw
[09:44] <evand> I'm assuming they're not in the admin group?
[09:45] <mebrown> I think it has been there for a little bit since I saw that yesterday too
[09:45] <mebrown> correct, not in admin group
[09:45] <mebrown> groups=1000(dell)
[09:45] <mebrown> bug against firstboot?
[09:45] <mebrown> shouldnt that user be  created as an admin, since there isnt any other way to log in as root, otherwise?
[09:45] <mebrown> that is how it used to work.
[09:45] <mebrown> at least in feisty
[09:46] <cjwatson> I think it's a bug in your image
[09:46] <cjwatson> it normally is given admin privileges
[09:47] <mebrown> pulled fresh today, saw the same thing yesterday
[09:47] <cjwatson> are you creating any other non-system users or groups?
[09:47] <mebrown> no.
[09:47] <cjwatson> mebrown: ok, is this from the alternate or desktop CD?
[09:47] <mebrown> create 'oem' user in preseed
[09:47] <mebrown> this is the live cd
[09:47] <mebrown> booted with oem-mode and preseed
[09:47] <cjwatson> can I have your preseed file?
[09:47] <cjwatson> without passwords
[09:48] <mebrown> yup.
[09:48] <mebrown> just a sec, I'll post it.
[09:48] <cjwatson> a bug report on oem-config would be the best avenue
[09:50] <mebrown> cjwatson, email address?
[09:50] <cjwatson> mebrown: https://bugs.launchpad.net/ubuntu/+source/oem-config/+filebug
[09:50] <cjwatson> but if you'd really prefer e-mail<EMAIL_ADDRESS>[09:50] <cjwatson> just that my inbox is a disaster area
[09:51] <mebrown> I'll file a bug
[09:51] <cjwatson> mebrown: I'm out for a bit now
[09:52] <cjwatson> fwiw
[09:53] <mebrown> just thought that would be the fastest way to get it to you
[09:53] <cjwatson> for the record, IRC is one of the worst possible ways to paste large quantities of stuff
[09:53] <mebrown> ok, sorry.
[09:53] <cjwatson> it sits there for ages gradually pasting line by line :-/
[09:54] <mebrown> just trying to figure out a quick way to get you the info.
[09:54] <cjwatson> anyway, have to go pick my wife up
[09:54] <mebrown> bug is being entered.
[09:54] <mebrown> have fun.
[09:55] <evand> mebrown: in the event that you do need to paste a large amount to IRC: http://pastebin.ubuntu.com/
[09:55] <mebrown> ah, yes. I forget about that...
[09:57] <mebrown> https://bugs.launchpad.net/dell/+bug/149582


[11:39] <penguin42> yofel: Bug 875660 as the cause of it wrongly selecting the HDMI
[11:39] <ubot4> Launchpad bug 875660 in pulseaudio (Ubuntu) (and 1 other project) "PA and knotify startup race leads to wrong device selection (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/875660
[11:40] <yofel> ah, thx
[11:40] <penguin42> I'll report it to KDE as well, since I know we don't really handle KDE bugs
[11:50] <yofel> penguin42: poke me once you've got the bug, it's probably an issue on the KDE side (as knotify should use phonon, not alsa...)
[11:53] <penguin42> yofel: Ah that makes sense
[11:55] <yofel> penguin42: as an estimate what happens: http://paste.kde.org/134299
[11:58] <penguin42> yofel:What's really annoying is I can't persuade PA to switch back to analog as default now I've restarted it's daemon
[12:01] <penguin42> ah, pacmd set-default-sink
[12:01] <penguin42> right, now I've got music - I can think
[12:09] <penguin42> yofel: KDE bug 284176
[12:09] <ubot4> KDE bug 284176 in general "knotify4 v pulseaudio startup race" [Normal,Unconfirmed] http://bugs.kde.org/show_bug.cgi?id=284176
[16:33] <AlexzAK> Hi, all... zeitgeist-daemon eating all my cpu!  I've upgraded to oneric couple hours ago
[16:33] <AlexzAK> What to do with it?
[18:15] <penguin42> any suggestions for bug 874975 - I put it into ubiquity because it was failure on 1st boot after install - but it could be nouveau?
[18:15] <ubot4> Launchpad bug 874975 in ubiquity (Ubuntu) "Ubuntu 11.10 does not start after instlallation [at Stopping userspace bootsplash] (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/874975
[19:00] <penguin42> why is 97513 a wishlist?
[19:00] <penguin42> bug 97513
[19:00] <ubot4> Launchpad bug 97513 in squid (Debian) (and 2 other projects) "Squid requires restart after Network Manager made connection to network (affects: 7) (dups: 1) (heat: 58)" [Unknown,New] https://launchpad.net/bugs/97513
[20:04] <bil21al> how can i get the patch on the app??
[20:40] <arand> bil21al: You may need to be a bit more specific?
[20:50] <bil21al> arand: what are you talking about?
[20:51] <arand> bil21al: what app? what patch? I meant.
[20:52] <bil21al> i didnt get you arand:
[20:53] <kyofel> bil21al: <bil21al> how can i get the patch on the app?? < what did you mean?
[20:54] <bil21al> like we reports the bugs and some time a patch is attached which is good . how can we get the patch of any application like if we want to get the patch of  banshee so how can i?
[20:55] <arand> You get the source of the application, patch it, and rebuild it into a new package.
[20:57] <bil21al> you mean the source code (the programming language)  is there any ubuntu wiki page for the study actually i m a IT student so thats why i was asking
[20:57] <jtaylor> bil21al: http://patches.ubuntu.com/
[20:58] <jtaylor> and for debian http://patch-tracker.debian.org/
[21:00] <arand> bil21al: Most wiki pages are actually based on the notion of you generating the patch/debdiff though, i.e. from a developers point of view...
[21:00] <bil21al> ok thankx
[21:01] <penguin42> one that might be worth looking out for on +1 upgrades; this one failed with [+0.18s] DEBUG: Failed to load session file /usr/share/xgreeters/lightdm-gtk-greeter.desktop: No such file or directory:   in the lightdm log - it hadn't installed the gtk greeter but was trying to use it
[21:02] <arand> bil21al: The last post of http://ubuntuforums.org/showthread.php?t=324672 is a reasonable outline of steps, https://wiki.ubuntu.com/PackagingGuide is very good, though not directly describing that task.
[21:04] <bil21al> thankx bro
[21:51] <Cheesehead> Anyone around know much about how Apport and core dumps?
[21:51] <Cheesehead> I have a Brainstorm idea that's beyond my technical depth, and I'm looking for some input: http://brainstorm.ubuntu.com/idea/28700/
[21:51] <Cheesehead> So I can moderate the idea properly.
[22:16] <hggdh> Cheesehead: what you want to know?
[22:17] <hggdh> Cheesehead: if apport is running, cores are automagically saved on /var/crash/, with additional metadata
[22:18] <hggdh> see apport-retrace for how to play with them, and apport-(gtk|kde) for how to run initial processing on them
[22:20] <hggdh> additionally -- again, if apport is running --, you get prompted for a bug submission (and all data, core amd meta, are uploaded to the bug)
[22:35] <Cheesehead> hggdh: Right, thany you. I have used Apport, and I checked the wiki page before coming here. The idea seems to be about renaming the core-dump filename for some kind of benefit that I don't quite get. So I ask.
[22:37] <Cheesehead> What I want to know is: Is he going about this the hard way? Is what he wants already handled by Apport and Launchpad appropriately? Is he talking about a valid use case?
[22:37] <Cheesehead> Or a corner case?
[22:52] <Cheesehead> I suspect the submitter is talking about pulling data from the bug report (of course, all my work has been on quite the other end)
[23:19] <penguin42> lightdm really isn't helping - it doesn't seem to put any diags to the screen when it fails


[20:03] <ofir> newz2000: can I ask you a question?
[20:09] <ofir> I understood that you are one of Ubuntu's site maintainers
[20:09] <ofir> Is it true?
[20:15] <thorwil> ofir: he's webmaster for ubuntu.com and canonical.com, afaik
[20:15] <ofir> Do you know when he is available here?
[20:17] <ofir> I mean, it seems that he is not away, however, he doesn't respond to messages written here
[20:17] <ofir> Maybe he is active in other room?
[20:29] <thorwil> ofir: lack of away state doesn't mean much. you should probably state your question and have patience (this applies to irc in general).
[20:30] <thorwil> oh, and consider it's sunday ;)
[20:30] <ofir> I know, but I am afraid that we have a long time differences
[20:31] <thorwil> middle of the usa for him
[20:31] <ofir> No matter...
[20:31] <ofir> Thanks!
[20:31] <thorwil> np


[21:19] <revolutionary> Hi Theodotos
[21:26] <theodotos[m]> Hi
[21:27] <revolutionary> How are you?
[21:27] <theodotos[m]> revolutionary: can I help?
[21:29] <theodotos[m]> I'm fine. Working late. :) How are you?
[21:29] <revolutionary> Hi again. How are you?
[21:30] <theodotos[m]> I'm fine again. Working late. :) How are you?
[21:31] <revolutionary> I'm fine, thanks :) I sent you 2 emails to different email addresses. Could you please take a look?
[21:32] <revolutionary> I need some help about LUKS on Debian
[21:34] <theodotos[m]> Ah OK :). You got me worried for a bit :)
[21:34] <theodotos[m]> Do tell.
[21:36] <revolutionary> Why i got you worried a bot :)
[21:36] <revolutionary> bit*
[21:37] <theodotos[m]> Receiving a mail asking information without much explanation. Standard phishers modus operanti :)
[21:39] <revolutionary> No no not phishing sir :)
[21:40] <revolutionary> If you look your emails i asked your GPG key for communicate securely..
[21:40] <theodotos[m]> Phew :)
[21:42] <revolutionary> I found your website while looking for information about LUKS
[21:42] <theodotos[m]> Ah, OK. Mail send.
[21:43] <revolutionary> You forgot to send the attachment :)
[21:45] <theodotos[m]> The mail is signed. Can't you imported like this?
[21:46] <revolutionary> I don't use any addon
[21:46] <revolutionary> So i can't see.
[21:47] <revolutionary> If you send with an attachment like .asc i can download that
[21:49] <theodotos[m]> OK. Try now.
[21:53] <theodotos[m]> Good?
[22:00] <revolutionary> Yes, good. I also added you in XMPP
[22:01] <revolutionary> Maybe i can ask in here
[22:01] <revolutionary> Email stuff is so long :)
[22:02] <revolutionary> i am trying to install Debian 10 Buster with LUKS but bit different scheme. This (https://www.youtube.com/watch?v=cchdw75WKXQ) guy is installing Ubuntu with Full Disk Encryption including /boot partition with detached header key in a USB drive. And i thought maybe i can do this on Debian 10 but i couldn't find any document or article about this. I am trying to achieve to install Debian with detached header key in a USB drive
[22:02] <revolutionary> on UEFI computer. And then i found some articles about this. Debian 9 wasn't supporting Secure Boot and many people was disabling Secure Boot in like these projects but now Debian 10 Buster support Secure Boot.
[22:03] <revolutionary> As i know Debian 9 wasn't supporting Secure Boot on Debian 9, but Debian 10 supports but i don't know how can i adapt that Ubuntu installation to Debian
[22:06] <revolutionary> sorry i gotta go now. please read this and i will come back later :)
[22:06] <revolutionary> have a nice night :)
[22:07] <theodotos[m]> I'm off to bed too.
[22:08] <theodotos[m]> I've read about encrypted boot, but never really tried it.
[22:09] <theodotos[m]> How about this?
[22:09] <theodotos[m]> https://cryptsetup-team.pages.debian.net/cryptsetup/encrypted-boot.html
[22:18] <theodotos[m]> revolutionary:  In case you get it working can I have your feedback? Or better yet, a guide?


[01:14] <Unit193> flexiondotorg: ..Are you pulling in metas or tasks?
[01:14] <flexiondotorg> Unit193, Well, meta via apt-get install ubuntu-mate-desktop^
[01:15] <Unit193> Ah, so tasks.  Ok.
[01:15] <Unit193> Great.
[01:15] <flexiondotorg> Because tasksel has proven to be very unreliable.
[01:15] <Unit193> Yeah we recommend ^ for -core installs.
[01:18] <flexiondotorg> Unit193, What about -desktop?
[01:18] <Unit193> flexiondotorg: We recommend people grab the ISO, but yeah would be fine there too.
[01:19] <flexiondotorg> Thanks.
[01:19] <flexiondotorg> I'm actually just making the task install function generic.
[06:33] <flocculant> bluesabre: re Raspberry - given that we have to fight tooth and nail to get what we really need tested - not interested in adding to that pile, secondly - if team decided to flail about with something new I really think the time will be post LTS not leading up to it
[06:46] <flocculant> bluesabre ochosi - marked ready
[06:48] <flocculant> ochosi bluesabre - thanks for comments re CSD - I thought that was the case, just needed confirmation :)
[06:48] <flocculant> also proving that sometimes I am listening ...
[07:06] <Unit193> \o/
[08:17] <flocculant> knome: on the getxubuntu page do we want to change 15.04 to read "The 15.04 release, codenamed Vivid Vervet, is a regular release and has support until January 2016." Now that we're adding 15.10 to that list?
[08:17] <flocculant> or remove 15.04
[08:18] <flocculant> I have moved 15.10 above 15.04 currently
[08:18] <flocculant> locally I hasten to add :p
[08:20] <flocculant> not being sure if I can change pages at x.org and then not update it till later so haven't
[09:33] <ochosi> flocculant: re: pi2, yeah, i tend to agree. at least if those were "official" builds that we would - again - get support requests for
[09:37] <flocculant> yup
[09:43] <bluesabre> ochosi, flocculant: thanks, that's also my standing
[09:43] <flocculant> that's lucky then :p
[09:44] <bluesabre> flexiondotorg: so, that's all three xubuntu-release folks... I'd suggest holding off on those pi2 builds for xubuntu
[09:44] <flocculant> and good morning bluesabre :)
[09:44] <bluesabre> good morning flocculant
[09:44] <bluesabre> thanks for marking the release ready
[09:44] <bluesabre> less to do this morning
[09:44] <flocculant> welcome
[09:45] <flocculant> yep - release notes done, website drafter - just needs some image thingy, getxubuntu page ready here
[09:46] <flocculant> all in all it's been quite relaxed end of cycle - at least for me :p
[09:46] <bluesabre> flexiondotorg: but thanks for the offer, we may choose to revisit that in the future
[09:46] <bluesabre> :)
[09:47] <flexiondotorg> bluesabre, OK, no problem :-)
[09:48] <flocculant> bluesabre: making a proper start today on updating our testcases - will get the tracker ready too
[09:49] <flocculant> so assuming they get xenial up pretty quick we'll be in a position to really push packages asap
[09:49] <bluesabre> flocculant: great!
[10:18] <flocculant> hi axwki_dave - thanks for testing for us :)
[10:19] <axwki_dave> Morning mate.. no probs.. I enjoy doing it.. gotta give something back to the community :-)
[10:19] <flocculant> :)
[10:20] <flocculant> there will be loads of opportunity to do that post-today :D
[10:20] <flocculant> we'll be really pushing people to test apps next cycle
[10:20] <axwki_dave> I Also try to get the testing word passed about using my twitter and G+ account
[10:20] <flocculant> that's awesome :)
[10:21] <axwki_dave> Thats good. Just permanatly set up a full test rig for that..  :-)
[10:22] <flocculant> excellent
[10:22] <flocculant> you know about the ppa's we use constantly?
[10:23] <flocculant> most of what we'll be pushing for XX is at http://xubuntu.org/contribute/qa/ under Exploratory Testing
[10:28] <flocculant> axwki_dave should hang about on irc more and get more involved in the behind the curtain stuff :p
[10:40] <axwki_dave> I do try to login while at work, got a vm with the latest release..  I'll take a look at the link cheers
[10:43] <axwki_dave> ooh.. I know what I'll be doing when I get home tonight...:-)
[10:45] <axwki_dave> so the ppas, I'll assume these will need to be installed on the latest release, rather than the latest test image?
[10:48] <flocculant> currently they work with all supported plus dev
[10:49] <flocculant> I don't think that will change
[10:49] <flocculant> obviously not going to work for xx just yet
[10:50] <flocculant> I guess I don't notice you if you're online but not actually talking :p
[10:50] <flocculant> only know you're here because I'd turned off hide joins/parts in here :)
[10:52] <axwki_dave> lol..
[10:55] <flocculant> bluesabre: you about still?
[11:00] <axwki_dave> be back in a bit off for lunch..
[11:00] <flocculant> sounds like a good plan - thanks :)
[11:27] <bluesabre> flocculant: hey
[11:28] <flocculant> bluesabre: quick question - one of those, never really used it so didn't miss it leaving
[11:28] <flocculant> no thumbnail support in catfish now ?
[11:29] <bluesabre> flocculant: click the cog to switch views
[11:29] <flocculant> \o/
[11:29] <flocculant> didn't see it hiding there - thanks :D
[11:29] <bluesabre> np
[11:29] <bluesabre> :D
[11:29] <flocculant> back to editing
[11:30] <bluesabre> http://i.imgur.com/lOHGJaH.png
[11:30] <bluesabre> fwiw
[11:31] <flocculant> :)
[12:03] <axwki_dave> too much food, just need to sleep now..
[12:04]  * flocculant is reading testcases and changing them to suit at least wily - feeling the same :p
[12:05] <axwki_dave> :-)
[12:34] <axwki_dave> well thats the ppa's (on this vm)and a trello account set up, will get the pp'a setup on my test drive for my laptop and the new dedicated test rig tonight.
[12:35] <axwki_dave> I'll be able to start doing the package testing on both 32 and 64 versions then
[12:35] <flocculant> great :)
[12:44] <axwki_dave> brb need to restart
[13:03] <flocculant> knome: so worked out from front page that we only have 1 regular at getxubuntu ...
[13:35] <flocculant> afternoon GridCube
[13:42] <GridCube> :) hello flocculant
[13:44] <akxwi_dave> howdo Grid.
[14:26] <flocculant> pleia2 knome - all the social stuff and the rest of the website needs to be done
[14:26] <flocculant> I did getxubuntu and published the release note
[14:29] <pleia2> others have access to social media, I'm not available for a couple weeks
[14:29] <flocculant> that's fine - I've no idea who so couldn't ping them
[14:30] <pleia2> https://wiki.ubuntu.com/Xubuntu/Contact/WebAdmins
[14:30] <pleia2> holstein has access to facebook, ochosi to g+ and knome on twitter
[14:30] <flocculant> yea - know knome and twitter
[14:31] <flocculant> ochosi: can you g+ release please
[14:32] <akxwi_dave> If you ever need anyone extra to help out on the Social/Web side, I'm an IT Manager and part time webadmin in a Law firm and can help
[14:32] <flocculant> then I suspect people would like the idea
[15:04] <flocculant> and hi slickymasterWork :)
[15:05] <slickymasterWork> :) hi
[16:00] <akxwi_dave> time for home.. have a good one
[18:14] <flocculant> bluesabre ochosi http://packages.qa.ubuntu.com/qatracker/milestones/350/builds/105268/testcases
[18:14] <flocculant> and anyone else half interested :)
[18:34] <dkessel> regarding the raspberry pi2: flexiondotorg, i would enjoy testing an xubuntu image :) but please don't spend much time on it just for me, as it looks as if the rest of the team is not too interested
[18:36] <dkessel> flocculant: good to see package testing set up for xenial :)
[18:36] <dkessel> also - we're the first to have it set up on the tracker :D
[20:13] <knome> huh, i'm back
[20:14] <knome> congrats everybody for the release
[20:16] <knome> http://tracker.xubuntu.org/
[20:16] <flocculant> knome: hi there - just passing through - didn't do any of the docs stuff on the processes obviously
[20:17] <knome> i'll look at them next
[20:18] <knome> ok - so
[20:19] <knome> the tracker is now tracking X
[20:19] <knome> the burndown should get its first line tomorrow, since that's the official starting day
[20:19] <knome> if you for some reason want to see wily stuff, go to http://tracker.xubuntu.org/?s=wily
[20:20] <knome> that data will keep on updating for some more time (at least today UTC), so people have time to mark items postponed or done or whatever
[20:20] <knome> other than that, carry on as usual
[20:21] <flocculant> got to like green already :p
[20:22] <knome> ahah
[20:23] <flocculant> package tracker is done - image appears to be waiting for images I suppose :p
[20:24] <flocculant> knome: you might notice I added widgets to the website processes - took me ages to remember what they were :D
[20:24] <knome> :D
[20:24] <flocculant> 16.04 XX  why XX and not xenial xerus :p
[20:25] <knome> you mean the toolbox menu
[20:25] <knome> i didn't know the name was announced
[20:25] <knome> usually it takes awfully lon
[20:25] <knome> g
[20:25]  * knome hides
[20:25] <flocculant> no - appearance - widgets
[20:25] <flocculant> oh yea name was up well early this cycle :p
[20:26] <knome> and updated
[20:26] <knome> flocculant, oh yeah, i did get the mail
[20:27] <flocculant> thought so
[20:27] <knome> sorry for being a bit unfocused, i have a headache
[20:27] <knome> >__<
[20:27]  * flocculant too
[20:27] <knome> and i didn't even fuss around with the release...
[20:28] <flocculant> knome: well tbh I'd marked pretty early today so had most of the day to sort bits
[20:28] <knome> :)
[20:28] <flocculant> Unit193: can you add package tracker too ;)
[20:28] <knome> Unit193, and work item tracker
[20:29] <flocculant> any need for ubottu in there?
[20:29] <knome> well it's the release schedule
[20:29] <knome> now that it's kind of in the tracker...
[20:29] <knome> don't know
[20:29] <knome> should update the blueprint with the dates so the burndown would pick them up
[20:30] <flocculant> oh right
[20:30] <flocculant> mmm
[20:31] <flocculant> is the schedule any use - wouldn't people involved know anyway
[20:33] <flocculant> anyway - I'm off now
[20:33] <flocculant> bluesabre: could we haz xenial ppa's :D
[20:33] <flocculant> now I'm really off - night all :)
[20:35] <knome> nighty flocculant! and thanks and congrats!
[20:46] <Unit193> knome: You going to poke people again?
[20:53] <knome> about...?
[20:54] <Unit193> Core MPs.
[20:54] <knome> when i don't have a headache and have time
[20:54] <knome> atm, looks like it's monday or later
[20:55] <Unit193> Trying to get it in before someone has to deal with rebasing.
[20:56] <knome> when would that seemingly happen?
[20:57] <Unit193> Very quickly, considering it has to happen before ISOs start cranking out.
[20:57] <knome> ok, i'll see if the headache goes away
[21:00] <Unit193> Sure.
[21:00] <Unit193> https://lists.ubuntu.com/archives/ubuntu-devel/2015-October/038937.html
[21:02] <knome> noticed
[21:05] <Unit193> knome: Wow, thanks.  Wasn't expecting it to be soon.
[21:05]  * knome shrugs
[21:05] <knome> seemingly the painkillers start to have some impact
[21:07] <ochosi> hey everyone! congrats on the release (and thanks for taking care of the formalities)
[21:08] <knome> hello ochosi and congrats that way too!
[21:08] <knome> another release within months!
[21:08]  * knome hides
[21:08] <ochosi> ;)
[21:09] <Unit193> Is there an informal page with things to update?
[21:09] <ochosi> flocculant: i'm taking a loko at the g+ page now
[21:09] <knome> loco at the g+ page
[21:09] <knome> Unit193, yeah.
[21:10] <knome> https://wiki.ubuntu.com/Xubuntu/Processes/Website
[21:11] <knome> but that page is obsolete partly, going editing
[21:11] <Unit193> And website team.
[21:13] <ochosi> flocculant: g-plused the release
[23:40] <Unit193> bluesabre: See sorinello's comment in #x, I think this is expected, but may be relavent.
[23:40] <Unit193> relevant*


[11:52] <yorick> cnd: "Max number of touches: 2"
[11:52] <yorick> but, how does windows get these multitouch gestures
[14:51] <cnd> yorick: applications can get multitouch gestures by using geis, which is our C wrapper around the gesture engine
[14:51] <cnd> there is also a qml library called oif-qml
[14:51] <cnd> and an older gtk library called libgrip
[14:51] <yorick> cnd: I just want something like touchegg (4-finger flicks for desktop switching)
[14:52] <cnd> yorick: ok, well touchegg theoretically should work for you for two touch gestures
[14:52] <cnd> however, you have to turn off "tap to click" and "two touch scrolling"
[14:52] <cnd> otherwise, the X server will process two touches for these features
[14:52] <yorick> cnd: how does it manage 3-touch gestures in windows?
[14:52] <cnd> what do you mean?
[14:53] <yorick> cnd: under windows I have 3-touch gestures just fine
[14:54] <cnd> your trackpad probably provides locations for two touches
[14:54] <cnd> and then says there are actually three touches in total
[14:54] <cnd> this is very typical for synaptics trackpads
[14:54] <cnd> our stack doesn't support three touches for these trackpads, but it is possible to add in support
[14:55] <cnd> unfortunately, it would first require adding support to the X server
[14:55] <yorick> is it a hardware limitation?
[14:55] <yorick> oh, I see
[14:55] <yorick> goddamnit, HP.
[14:56] <yorick> "see, it's multi-touch, it can keep track of TWO fingers at once!"
[17:10] <cnd> yorick: yeah (sorry for the late response)
[17:11] <cnd> for a long time, apple was the only company putting out real full multitouch devices
[17:46] <yorick> cnd: what companies have them now?
[17:46] <cnd> synaptics has full multitouch now
[17:46] <cnd> on their latest models
[17:47] <cnd> I'm not sure of others


[00:25] <bluebomber> Hey, everyone.
[01:21]  * LoyalWolf-AFK is away: sleeping, or out.
[03:19] <bluebomber> Hey, flocos!
[03:19] <bluebomber> Does anyone know if there's a way to restore the "old" alt-tab behavior in 11.10? I don't want alt-tab to cycle through apps on ALL workspaces...
[03:31] <maxolasersquad_h> bluebomber: Unity is not workspace aware at present.  That was discussed at UDS, and there seemed to be agreement that it should be in Pangolin, but I don't think that was ever set a defenitive goal.
[04:48] <bluebomber> Wait, wait... wasn't it workspace aware in 11.04?!
[04:48] <bluebomber> I don't remember this alt-tab behavior then...
[08:46] <bluebomber> govatent!
[12:30]  * LoyalWolf-AFK is back (gone 11:08:29)
[20:17] <bluebomber> Good afternoon, everyone!
[20:17] <bluebomber> Philosorapter asks: maxolase1squad and maxolasersquad_h.... same person?
[21:45] <maxolasersquad_h> Philosorapter: indeed