[00:22] <wxl> so i want to build the latest kpmcore from upstream git master… what's the best way to do that exactly?
[00:26] <wxl> i mean i could just do it but ultimately i'd like a packaged version
[00:26] <wxl> but i'm not sure exactly how to trick e.g. watch into behaving correctly
[01:22] -lugito:#lubuntu-devel- [T129: Lubuntu 18.04.4] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T129#3095
[01:23] -lugito:#lubuntu-devel- [T129: Lubuntu 18.04.4] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T129#3096
[01:26] -lugito:#lubuntu-devel- [T129: Lubuntu 18.04.4] kc2bez (Dan Simmons) commented on the task: https://phab.lubuntu.me/T129#3097
[01:27] -lugito:#lubuntu-devel- [T129: Lubuntu 18.04.4] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T129#3098
[01:30] <kc2bez> wxl: What is in the watch file now for kpmcore? I haven't even glanced.
[01:30] <wxl> kc2bez: presumedly something that's looking for a released version XD
[01:31] <kc2bez> Maybe, it is more likely tied to the changelog version though.
[01:31] <wxl> hm
[01:32] <wxl> but still how would it know which git commit to grab?
[01:32] <wxl> sorry i've never had to deal with anything but released cersions
[01:33] <kc2bez> typically me neither but I think you can add a +gitCOMMIT or +gitDATE or something to the version.
[01:33] <wxl> you know where that's documented?
[01:33] <kc2bez> no!
[01:33] <wxl> :/
[01:33] <kc2bez> maybe I can find an example
[01:34] <wxl> oh hm https://salsa.debian.org/qt-kde-team/extras/kpmcore/blob/debian/4.0.1-2/debian/watch
[01:35] <wxl> so i'd have to start by swapping that over to github
[01:35] <kc2bez> Raman did it here for globalkeys https://phab.lubuntu.me/source/lxqt-globalkeys/browse/ubuntu%252Ffocal/debian/changelog$38
[01:35] <wxl> looks like just with a version
[01:36] <wxl> strange
[01:36] <wxl> i mean it seems to be date based but how would it know which commit from that date?
[01:36] <wxl> non-determinism yay
[01:37] <kc2bez> Not sure, beyond my current knowledge.
[01:37] <kc2bez> Was hoping to help though.
[01:37] <wxl> you got me a little closer
[01:40] <kc2bez> same deal here it looks like https://salsa.debian.org/debian/screenfetch/blob/debian/sid/debian/changelog#L20
[01:49] <kc2bez> If I read the following properly you can download the tar and run uupdate https://www.debian.org/doc/manuals/maint-guide/update.en.html#newupstream
[01:50] <kc2bez> less automation there though
[02:21] -lugito:#lubuntu-devel- [T129: Lubuntu 18.04.4] guiverc (Chris Guiver) commented on the task: https://phab.lubuntu.me/T129#3099
[02:35] <guiverc> first i386 install 18.04.4; gui hasn't appeared.. 
[02:35] <lubot> <kc2bez> oof
[02:36] <guiverc> ps doesn't see lightdm  (service -status-all shows "-")
[02:37]  * kc2bez searches for a USB drive
[02:39] <guiverc> maybe my machine specific; i see a systemd-journald file /var/log/journal... corrupted or uncleanly shut down, renaming and replacing... I may need to verify my chosen partition... I'll try re-install to a different drive..
[02:40] <kc2bez> I will give it a go too. I think that the two of us might be the only ones with 32 bit hardware on the team. 
[02:40] <guiverc> `sudo service lightdm start` would cause term to switch to gui, but nothing again.. back to term and service wasn't running...   I'll use different drive..
[02:41] <guiverc> by switch to gui I didn't mean gui, switch to (blank with cursor as if starting gui)... never saw the gui
[03:05] <guiverc> kc2bez, a re-install on different drive worked !!!  
[03:06] <guiverc> I'll have to badblocks the other drive before I confirm hardware is an issue, but i have success (it was faster installing.. same box, just different drive..)  I'll move to other tests for now..
[03:10] <kc2bez> Ok sounds good. I am almost through an install as well. 
[04:10] <wxl> good call, @kc2bez. that''s what i needed. now if i can get i tot work correctly
[04:11] <wxl> https://paste.ubuntu.com/p/c6xzqVDHm5/
[04:13] <wxl> dh $@ --with pkgkde_symbolshelper
[04:13] <wxl> harumph
[04:14] <lubot> <tsimonq2> That's because you explicitly list that path in an install file and it's no longer being produced so it can't be installed
[04:14] <lubot> <tsimonq2> Grep all the install files for that path and remove it
[04:14] <wxl> that's what i wass thinking 
[04:15] <wxl> hey @tsimonq2 while you're here do you know anywhere that there's policy for versioning git snapshots?
[04:16] <lubot> <tsimonq2> @wxl [<wxl> hey @tsimonq2 while you're here do you know anywhere that there's policy f …], There's unspoken policy
[04:16] <wxl> figured as such
[04:16] <lubot> <tsimonq2> last.tagged.version+gitYYYYMMDD-0ubuntu1
[04:16] <wxl> @tsimonq2: why do i so often see gitDATE rather than gitHASH?
[04:17] <lubot> <tsimonq2> I personally always do gitDATE to make sure I don't accidentally get a lower version number
[04:17] <lubot> <tsimonq2> I think that's gbp though
[04:17] <wxl> hm
[04:24] <wxl> oh what the heck
[04:24] <wxl> dpkg-source: error: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address
[04:25] <wxl> i mean there's an obvious fix but that seems like a hack
[04:25] <wxl> i mean this is supposedly our packaging. we've had ubuntu changes before
[04:26] <wxl> well i guess not of 4
[05:25] <wxl> good lord 228 build machines on the farm and 206 are disabled
[05:25] <wxl> what is up with THAT?
[05:40] <wxl> omg there is *one* amd64 builder jeeez
[06:12] <guiverc> I'm assuming this is expected; clicking RELEASE NOTES results in 18.04.3 being displayed
[07:49] -lugito:#lubuntu-devel- [rMANUAL9d02b8184cb4: Add what left arrow actually does] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL9d02b8184cb4
[07:57] <guiverc> :(  I see issues by leok (keyboard layout, haven't experienced it, but I use US layout as an aussie)
[09:33] <lubot> <kc2bez> @guiverc [<guiverc> I'm assuming this is expected; clicking RELEASE NOTES results in 18.04 …], The link to the Ubuntu notes? I noticed the same.
[09:46] <lubot> <kc2bez> @guiverc [<guiverc> :(  I see issues by leok (keyboard layout, haven't experienced it, but …], reading the report, 20.04 is mentioned yet it seems to be filed under 18.04.4
[09:57] <guiverc> Yes the 20.04 ref grabbed me; i assumed it was a problem that first occurred with newer kernels (thus 20.04 now appearing in later 18.04 stack), but I didn't read that far... I had my own i386 fails at the time..  (really minor though; about to file another when I'm returned to 'live'; not blockers in my mind at all)
[09:58] <lubot> <kc2bez> Good to know, thanks guiverc
[12:19] <kc2bez> guiverc: It looks like we have an issue with auto resizing on 32 bit based on your reports.
[12:20] <guiverc> it's all on the one box.. maybe it's something weird on that box (I do hate that era hp's BIOS config)
[12:21] <guiverc> how many x86 users will use auto-resize anyway... yeah it's strange i had issues with that two rather different ways too
[12:22] <kc2bez> I can do a test too, it may be a bit later today.
[12:22] <guiverc> :)  thanks... 
[12:23] <kc2bez> I anticipate a respin though
[12:24] <kc2bez> https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1861794
[12:24] <ubot93> Launchpad bug 1861794 in linux-signed-hwe (Ubuntu) "[18.04.4] System boots in insecure mode after an installation with SB on" [Undecided, New]
[12:24]  * guiverc does not want to hear that !!!
[12:24] <kc2bez> Maybe I will be wrong
[12:24]  * guiverc may have fingers crossed    (i expect it regardless...)
[12:24] <kc2bez> I am "new" around here still.
[12:25] <guiverc> me too
[12:25] <guiverc> I've been around news for years; but not lubuntu for that long
[14:50] <lubot> <The_LoudSpeaker> I was mentioned wxl ?
[14:52] <lubot> <The_LoudSpeaker> Also, sorry @HMollerCl I said I would test the script. But I am having some issues with internet. can't download the latest iso to check in it. I will do the test as soon as I have good internet.
[15:14] <lubot> <HMollerCl> @The_LoudSpeaker [Also, sorry @HMollerCl I said I would test the script. But I am having some issu …], You don't need the latest iso
[15:15] <lubot> <The_LoudSpeaker> I know. But the install in my vm is a bit messed up. I have to do a reinstall. And I need a iso to do that.
[16:26] <lubot> <The_LoudSpeaker> Okay. I just managed to get today's iso. … There was something to check related to replacing partition during installation na? @wxl23 @kc2bez
[16:28] <wxl> i think you're making stuff up
[16:28] <wxl> there was a mention about bionic auto-resize on a 32 bit, but there's a respin pending we think
[16:29] <lubot> <The_LoudSpeaker> @wxl [<wxl> i think you're making stuff up], 🙄 I remember reading something similar here or on discourse. But lite now.
[16:30] <lubot> <The_LoudSpeaker> Also, will zfs be supported in focal?
[16:30] <wxl> well erase disk with an existing partition fails in focal but that's known
[16:30] <lubot> <HMollerCl> wxl: which is teh easiest way to make a broadcom work?
[16:30] <wxl> well zfs ISN'T supported in ubuntu so no (the option is totally experimental)
[16:30] <wxl> @HMollerCl depends on which one. some are really easy and some are a total pain.
[16:30] <wxl> !b43
[16:30] <ubot93> Help with Broadcom bcm43xx can be found at https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx
[16:31] <wxl> ^ that's helpful
[16:31] <lubot> <The_LoudSpeaker> @wxl [<wxl> well erase disk with an existing partition fails in focal but that's known], Ouch. Should have said just a min ago. I started with manual partitioning and a btrfs partition. Nvm will check on next install.
[16:31] <wxl> this too @HMollerCl https://wireless.wiki.kernel.org/en/users/Drivers
[16:31] <lubot> <The_LoudSpeaker> @wxl [<wxl> well zfs ISN'T supported in ubuntu so no (the option is totally experiment …], Will we be also giving that option? For those who want to experiment?
[16:31] <wxl> no need to check. it's a known failure and we have a pending fix
[16:32] <lubot> <The_LoudSpeaker> @ubot93 [<ubot93> Help with Broadcom bcm43xx can be found at https://help.ubuntu.com/comm …], This worked with me.
[16:32] <wxl> no we won't be offering it yet https://github.com/calamares/calamares/issues/533
[16:32] <ubot93> Issue 533 in calamares/calamares "ZFS support" [Open]
[16:33] <lubot> <The_LoudSpeaker> K.
[16:35] <lubot> <HMollerCl> thanks wxl
[16:35] <lubot> <HMollerCl> I thought it was easier now...
[16:37] <wxl> for some cards it's very easy
[16:37] <wxl> for others, no.
[16:41] <lubot> <The_LoudSpeaker> @wxl [<wxl> for others, no.], +1
[16:41] <lubot> <The_LoudSpeaker> @HMollerCl any prerequisites for the script? Do I have to have something Installed?
[16:43] <lubot> <kc2bez> @wxl [<wxl> there was a mention about bionic auto-resize on a 32 bit, but there's a re …], That's only my guess at this point. Other than the bug I referenced I don't have anything to base it on.
[16:44] <lubot> <HMollerCl> @The_LoudSpeaker [@HMollerCl any prerequisites for the script? Do I have to have something Install …], Python and qt5, which you should already have
[16:45] <lubot> <HMollerCl> Python3
[16:45] <lubot> <The_LoudSpeaker> @HMollerCl [Python and qt5, which you should already have], K. Will test and give my comments later.
[16:46] <wxl> there is only python3 :)
[16:48] <lubot> <teward001> @wxl [<wxl> there is only python3 :)], The Python 2 is dead, there is only the Python 3.  All Hail the Python!  *shot*
[17:21] <wxl> re that issue with the erase disk/focal problem i have a git master kpmcore and a git master cala rebuilt against it in ppa:wxl/testy-testy 
[17:21] <wxl> well cala is building
[17:21] <wxl> supposedly the latest kpmcore has a potential fix
[18:00] <lubot> <franksmcb> @wxl [<wxl> there was a mention about bionic auto-resize on a 32 bit, but there's a re …], I can confirm that it effects Ubuntu MATE as well on 32bit
[18:01] <wxl> @franksmcb well that's reassuring. you know of a bug? cc @kc2bez @guiverc
[18:04] <lubot> <franksmcb> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861912
[18:05] <wxl> you the man :)
[18:07] <wxl> ^ @RikMills can you confirm in Kubuntu i386?
[18:08] <RikMills> not right now
[18:11] <kc2bez> guiverc had a couple of bugs too https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861777  and  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1861788 but he wasn't sure if that was his box only that was having an issue.
[18:11] <ubot93> Launchpad bug 1861777 in ubiquity (Ubuntu) "Lubuntu 18.04.4 QA-test; I cannot select which drive I want to install to" [Undecided, New]
[18:11] <ubot93> Launchpad bug 1861788 in ubiquity (Ubuntu) "Lubuntu 18.04.4 QA-test install; post-install it failed to boot - grub rescue" [Undecided, New]
[18:11] <wxl> yeah i saw those but i need his help sorting them out
[18:12] <kc2bez> Also we have this https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1706859 which is a bit confusing as to which version it actually relates too.
[18:12] <ubot93> Launchpad bug 1706859 in ubiquity (Ubuntu Bionic) "Auto-selected keyboard layout no longer matches chosen region on 'Where are you' page" [Medium, Triaged]
[18:14] <kc2bez> Thanks for the assist @franksmcb
[18:16] <lubot> <franksmcb> No worries Dan. I'm lugging around the crusty old laptop today for just this reason. :)
[18:34] <kc2bez> @franksmcb Would you be willing to run that same test on a 18.04.3 image?
[18:37] <lubot> <franksmcb> @kc2bez [<kc2bez> @franksmcb Would you be willing to run that same test on a 18.04.3 imag …], I can. That system did run those iso tests previously and was successful. Give me a few
[18:39] <kc2bez> Thanks Bill, appreciate it.
[19:05] <lubot> <franksmcb> 18.4.3 point release installs correctly using auto-resize. … Ran SMART tests on disk and it shows OK.
[19:05] <lubot> <franksmcb> Slow going on the installs :P
[19:05] <kc2bez> Thanks for running that.
[19:06] <kc2bez> I know, I ran a couple of spot checks last night.
[19:06] <kc2bez> If you could update the bug with that info that would be cool @franksmcb
[19:07] <lubot> <franksmcb> Done. Tis frustrating that I don't have logs for the error
[19:10] <wxl> looks like the kpmcore update is a bust :(
[19:11] <kc2bez> :(
[19:11] <kc2bez> Sorry wxl
[19:13] <wxl> @franksmcb you could use apport-collect, but you'd need to go reproduce the problem and then do it ideally
[19:13] <wxl> presumedly the "lock" you refer to is simply in ubiquity rather than the whole system
[19:16] -lugito:#lubuntu-devel- [T129: Lubuntu 18.04.4] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T129#3102
[20:10] <lubot> <franksmcb> wxl I've set up the system to reproduce it. And as before it hard locks...I can't even drop into a TTY.
[20:24] <wxl> @franksmcb wow jeez that sucks
[20:24] <lubot> <franksmcb> It's odd and frustrating
[20:25] <wxl> well it's been escalated in #ubuntu-release, so we'll see
[22:34] <lubot> <franksmcb> I've gotten a comment on the bug that someone was able to reproduce it
[22:34] <wxl> yeah they're working on it in #ubuntu-release