=== genii is now known as genii-core [04:28] #kubuntu /topic still announces the 21.04 release [04:50] tomreyn: whoops. thanks [04:52] RikMills: maybe the 20.04 point release, too? i'm not sure where we're at. [04:52] oh thats gone, ok [04:55] tomreyn: 20.04.3 IIRC. I'll soert that later [04:55] *sort [07:44] RikMills: can you please put that on hold until we have time to discuss a better strategy [07:45] santa_: I have done most of them now, so may as well finish [07:45] sigh [07:45] look, this unilateral decisions you are making are not specially motivating [07:47] and I have a life and it's not specially motivating - to say the least - to spend a fair amount of hours fixing warnings to see how you import 10 or so in a day [07:47] also, the same applies to fixes that get overriden by one of the many, worthless, pointless syncs [07:48] if useful delta got missed, I will fix that [07:49] that's a plain waste of time [07:49] + the risk of breaking things [07:49] I am not syncing/merging breaking changes [07:49] look, we had a workflow FOR A REASON [07:50] then, you, you alone, without discussion, decided you know a lot better [07:51] one of the points of doing merges from debian with git is, precisely, to reduce the risk of dropping changes accidentaly + not having to fix the same thing again, again, again and again [07:53] if I accidentally drop something important, I will fix it [07:54] have you read anything that I wrote above? [07:54] have you? [07:54] 1. that's a plain waste of time [07:55] 2. you are, unnecesarily, introducing the risk of breaking things [07:56] 3. given the risk above you may break things without knowing, do you even check the status reports before mering? [07:56] * merging [07:57] so the summary of this wonderful "strategy" of the debian syncs [07:57] - more work [07:57] - worse results [07:58] so let's see: hmmm, more cost of maintenance for worse results [07:58] sounds like economy nobel prize or something [07:59] 1. disagree, but I don't mind spending the time [07:59] 2. disagree, but if it happens I will fix it [07:59] 3. I plan to do a full QA run when done [08:01] haha, absolutely great [08:02] would you do the same if you were doing this for a company? [08:02] or even better [08:03] do you behave the same way at paid work? [08:04] do you? [08:05] "this is a waste of time, but I don't mind spending the time and I don't mind wasting the time of others?" [08:06] not true, as already stated [08:06] what is the point of the syncs? [08:07] (instead of merges) [08:07] what is the point of merges with useless delta? [08:07] 1. not having to re-apply our changes [08:08] 2. reducing the risk of breaking things [08:08] 1. if I accidentally drop something important, I will fix it [08:08] 2. see 1. [08:09] 1. no, you don't [08:09] 2. see 1. [08:09] and if you do, how come powerdevil is still broken? [08:10] how come each time you do a frameworks release, "misteriously" a big bunch of new warnings appear? [08:11] how is pd broken? [08:12] and even if you bother to apply, re-apply and re-re-re-aply our changes, THAT'S A PLAIN WASTE OF TIME [08:12] lintian is constantly adding new warnings. some or trivial [08:13] and you are making the problem worse [08:13] how is pd broken? [08:13] instead of fixing current warnings, you are adding even more [08:13] about powerdevil [08:13] please see: [08:13] http://tritemio-groomlake.duckdns.org/build-status/buildstatus_ubuntu-exp3/ubuntu-exp3_status_plasma.html [08:14] I bothered to do a workaround for that some time ago [08:17] ah, I would see that when I do the QA [08:17] just to see how it's gone now, as usual [08:17] I thought you meant it was actually 'broken' [08:18] aha, so you don't mind about warnings [08:18] well, the problem with warnings is that they hide real issues if we have too many [08:19] which is what is happening at the moment [08:20] and let me insist: what is the point of syncs? [08:20] because I still fail to see how is that good for our users [08:21] while I see a lot of nitpiking imported from debian + new warnings (like if we didn't have enough warnings already) [08:22] and that increases the cost of maintenance [08:23] and that means, at some point, giving a worse service to our users [08:25] https://launchpad.net/ubuntu/+source/powerdevil/4:5.23.3-1ubuntu2 [08:25] thanks [13:27] Hi folks [22:36] if anyone running impish backports wants to test the Gear (formally apps) 21.12 RC, the it is in ppa:kubuntu-ppa/expermintal [23:05] I am glad I have not migrated to JJ yet. So, I added the repository to 21.10 using apt, updated using Discover, re-booted my VM, I used Discover to install Konqueror 21.11.90, and it worked. Also tested were: Dolphin, Klondike, Kmines, Konsole, and Kate. [23:06] \o/ [23:09] nice [23:10] it is all uploaded to JJ as well, but some may be stuck in proposed due to test infra issues [23:27] In JJ, it would be in the main repos?