[00:32] <barry> cyphermox: ping, re: dbusmenu (maybe)
[00:32] <cyphermox> barry: pong
[00:33] <barry> cyphermox: after the last update, two of my applications lost their global menu.  iirc there was a new dbusmenu uploaded recently, and i was wondering if that could be the culprit.  the apps are emacs and claws-mail
[00:35] <cyphermox> it's not impossible but it's the second time I hear about this today
[00:35] <cyphermox> not that I do much on dbusmenu ;)
[00:35] <barry> cyphermox: yeah, i was going to ping tedg, but he's offline and you're next on my "hey, i recognize that guy on the dbus menu team" :)
[00:35] <barry> cyphermox: i'm just wondering where i should report the bugs.  reporting them on emacs and claws-mail probably won't get much attention ;)
[00:36] <cyphermox> barry: check if UBUNTU_MENUPROXY is set in your environment
[00:36] <cyphermox> barry: I'd say either unity or libdbusmenu?
[00:38] <cyphermox> barry: I wonder if the correct place for the bug isn't indicator-appmenu
[00:38] <barry> % echo $UBUNTU_MENUPROXY
[00:38] <barry> 1
[00:39] <barry> ;)
[00:39] <barry> (although that's definitely not a new setting)
[00:39] <cyphermox> nah, it's not
[00:39] <barry> cyphermox: i guess it should be set, right?
[00:39] <cyphermox> robru: did you fix that on your system ^ ?
[00:40] <cyphermox> barry: yes, it should be
[00:40] <cyphermox> that just means to use them
[00:40] <cyphermox> (global menus)
[00:40] <barry> i vaguely remember that ;
[00:40] <cjwatson> oh hey, you could fix up the libdbusmenu ftbfs :)
[00:40] <cyphermox> barry: robru asked about this earlier too, but I'm not sure if he fixed it
[00:41] <cyphermox> cjwatson: I could try, but I'd do that only in a few hours
[00:41] <cjwatson> I think it's http://paste.ubuntu.com/7111413/ (following https://bugzilla.gnome.org/show_bug.cgi?id=701638, you might want a different approach, not sure) plus documenting the symbols that it complains about now)
[00:41] <robru> cyphermox, barry no never got it fixed
[00:41] <robru> barry what symptoms are you seeing?
[00:41] <cjwatson> easier with my mp to make the test suite verbose
[00:41] <cyphermox> I'm trying to go to bed very soon, I will need to be up in very few hours
[00:41] <cjwatson> sure
[00:42] <cjwatson> just hoping to hand off one of the zillion things I've been working on today to somebody with more clue about it :)
[00:42] <cyphermox> should be simple enough to fix yeah
[00:43] <barry> robru: both emacs and claws have lost their global menu.  go to the global menubar and the app name never fades into the menu
[00:43] <barry> robru: this definitely worked a few days ago.  those are the only two apps that i've identified so far as busted
[00:44] <cyphermox> cjwatson: ftbfs where? I don't see it in LP or on ubuntuwire?
[00:44] <robru> barry, ok, i'm having the same symptoms on *every* window. I have zero menubar integration right now. luckily the traditional menubars are showing up so apps are usable, just ugly
[00:44] <cjwatson> cyphermox: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140307-trusty.html
[00:44] <cyphermox> oops
[00:44] <cjwatson> cyphermox: also https://jenkins.qa.ubuntu.com/job/libdbusmenu-trusty-amd64-ci/8/console
[00:45] <barry> robru: interesting.  chromium seems okay
[00:45] <barry> ff seems okay
[00:45] <barry> gtimelog seems okay
[00:45] <robru> barry, lol, chromium is particularly bad, I get a unity titlebar around the chromium window. no menus either. nor ff
[00:49] <barry> robru: have you filed a bug?
[00:49] <robru> barry, not yet, haven't had time to troubleshoot and I wasn't sure if it was something I broke myself (i was tinkering a bit around the time it broke)
[00:50] <barry> robru: naw, it's at least also partially broken for me too.  i'll ping tedg in the morning (if he's around)
[00:50] <robru> barry, ok. please email me the bug and I'll mark it as affecting me
[00:50] <robru> when you do eventually file it ;-)
[00:51] <barry> robru: +1
[01:03] <cyphermox> barry: does gedit not show menus either?
[01:04] <barry> cyphermox: it does
[01:04] <cyphermox> ah
[01:04] <cyphermox> but not firefox and others
[01:05] <cyphermox> I'm mixing things up, sorry, I see, only claws and emacs
[01:06] <barry> cyphermox: well, ff and chrome work for me.  just claws and emacs broken (so far)
[01:25] <TheMuso`> barry: Is emacs using GTK2?
[01:26] <TheMuso`> Firefox works because it has a special plugin to work with the menus... But if emacs is GTK2, there is a chance that other GTK2 apps are broken as well, I assume claws is GTK2 also...
[01:28] <barry> TheMuso`: i bet you're right that both claws and emacs are using tgk2
[01:28] <barry> *gtk2
[01:28] <barry> TheMuso`: hmm, maybe not: libgtk-3-0 (>= 3.2.1)
[01:28] <barry> that's emacs24
[01:29] <TheMuso`> Hrm ok.
[01:29] <barry> claws-mail is though: libgtk2.0-0 (>= 2.24.0)
[01:44] <TheMuso`> barry: Well I have just confirmed its not all GTK2 apps, I just tried one now and menus behave as normal.
[01:50] <barry> TheMuso`: hmm.  okay
[03:21] <infinity> barry: Asking the obvious question, have you logged out or rebooted since your last upgrade?  I've noticed that upgrades to the menu stuff seem to do weird things to active sessions sometimes.
[06:36] <pitti> Good morning
[06:36] <pitti> sarnold: bah, 'connecting to Launchpad failed: unclosed token: line 16399, column 6'; yay
[06:37] <pitti> sarnold: I wonder why that started happening so often; it has worked for years without such cache problems..
[06:37] <pitti> sarnold: thanks for pointing out, restarting
[06:38] <pitti> RAOF: I think you actually want to use umockdev for the recording
[06:38] <RAOF> pitti: Yeah, ish.
[06:39] <pitti> RAOF: otherwise I'd have to add the whole ioctl decoding and evemu .desc parsing/ioctl synthesis
[06:39] <RAOF> Right.
[06:39] <pitti> RAOF: so with umockdev being able to record and read .events files it should be fine, right?
[06:39] <RAOF> Yeah, mostly.
[06:39] <pitti> RAOF: ah, what's missing?
[06:39] <pitti> RAOF: ioctls should  be fine
[06:40] <pitti> (on same endianess, anyway)
[06:40] <RAOF> It just kinda irks me that if I change the order, or set of ioctls that I use, I need to re-record.
[06:40] <RAOF> (Not that I've had to do that, just reading the code that's what I think happens)
[06:40] <pitti> RAOF: no, umockdev's recorded ioctls don't need to be replayed in order
[06:41] <RAOF> Ah, sweet. I guess I mis-skimmed the code.
[06:41] <pitti> RAOF: in fact, evdev ioctls are all independent from each other, so you can call them in any order and any number you like
[06:41] <RAOF> pitti: In which case I could probably just umockdev evemu-record, right?
[06:41] <pitti> RAOF: .record must exactly match the original; .ioctl is a tree
[06:41] <pitti> RAOF: well, yes; it's a bit redundant, though :)
[06:42] <RAOF> pitti: Only if you've already implemented the ability to record .events as well as replay them :)
[06:42] <pitti> RAOF: so, I'll clean up .events reading this morning and then look into .events writing; that should be fairly easy
[06:42] <RAOF> Bitchn'
[06:42] <pitti> reading is more work (that's why I started with that)
[06:42] <RAOF> Ah, cool. Thanks muchly!
[07:20] <pitti> RAOF: does that description make sense to you, or is it confusing somehow? http://paste.ubuntu.com/7112693/
[07:25] <pitti> RAOF: refined: http://paste.ubuntu.com/7112707/
[07:34] <pitti> zul: apparently the new python-taskflow is missing some new dependencies? (autopkgtest failure)
[07:50] <pitti> cjwatson: pkgbinarymangler fixed; it was an actual regression, but a corner case (handling of files containing '%'); bash 4.3 apparently got a stricter escaping behaviour
[08:03] <Noskcaj> mlankhorst, Would you mind fixing the libgphoto b-dep of wine1.6?
[08:31] <dholbach> good morning
[08:38] <mlankhorst>  morning
[09:31] <RAOF> pitti: Description looks good. Is there any way we can shoe-horn a default-device into the evemu format? :)
[09:31] <cjwatson> pitti: thanks
[09:31] <pitti> RAOF: the documentation doesn't document it; but I'd expect "# comment" lines to work
[09:32] <pitti> RAOF: (i. e. they work with umockdev, not sure if they work with evemu itself)
[09:32] <RAOF> Yeah, they won't work with evemu, because it doesn't make sense - evemu creates a new uinput device to replay through.
[09:32] <pitti> RAOF: I mean if evemu will ignore comment lines
[09:33] <RAOF> Oh, right.
[09:33] <RAOF> Eh.
[09:33]  * RAOF is not particularly interested in that.
[09:33] <pitti> RAOF: I just don't want to claim "it writes an evemu .events file" when that file can't be used with evemu
[09:34] <pitti> RAOF: ah, seems it does
[09:34] <pitti> i. e. '#' comments are fine
[09:36] <RAOF> Sweet.
[09:50] <Saviq> diwic, hey, question about the "what did you plug in" dialog: I have a combo jack (Dell Latitude E6420), but I never get the dialog, nor do I ever actually get mic input from the headset, is there something I could provide you with that needs to be added to some hw quirks or something to fix that?
[09:51] <diwic> Saviq, sure, start with alsa-info: https://wiki.ubuntu.com/Audio/AlsaInfo
[09:52] <Saviq> diwic, http://www.alsa-project.org/db/?f=449823acea2249ba25ab19e793c91858f4965769
[09:53] <Saviq> diwic, want me to file a bug (against ?) with that?
[09:53] <diwic> Saviq,
[09:53] <diwic> Kernel release:    3.11.0-12-generic <- any reason you're not running a 3.13 kernel?
[09:54] <Saviq> diwic, good question, no
[09:55] <Saviq> hmm update-grub doesn't find the kernel...
[09:55] <Saviq> ah, 'cause it's not there, must've dropped linux-generic at some point
[09:55] <diwic> Saviq, and second, your machine is not one of the affected ones, at least not at this point...is it Certified/Enabled by Canonical?
[09:56] <Saviq> diwic, yeah http://www.ubuntu.com/certification/desktop/models/?query=6420&category=Desktop&category=Laptop&level=Any&release=
[09:57] <Saviq> diwic, they're not *exactly* like mine is - I've nVidia with Optimus
[09:58] <mardy> cjwatson: hi! About https://code.launchpad.net/~cjwatson/libaccounts-glib/multiarch/+merge/211468, it's the first time I see Multi-Arch so my question might not make much sense:
[09:58] <mardy> cjwatson: don't we need a similar line for the -dev package?
[09:58] <diwic> Saviq, so it's a computer from 2010? Has the Mic worked in previous releases?
[09:59] <Saviq> diwic, yeah, it's an old one, and I can't say that it ever worked
[10:00] <Saviq> diwic, it's definitely only using the internal mic now
[10:00] <Saviq> diwic, I can try  a live saucy if you'd like
[10:01] <diwic> Saviq, when you submitted the alsa info, was a headset plugged into the jack?
[10:01] <Saviq> diwic, no, let me
[10:02] <Saviq> diwic, does it matter what do I plug in? i.e. headset vs. headphones?
[10:02] <diwic> Saviq, yes
[10:03] <diwic> Saviq, if I understand you correctly, plugging in headphones works as it should, whereas plugging in a headset you can't use the headset's mic?
[10:03] <Saviq> diwic, yes
[10:04] <Saviq> diwic, this is with a headset http://www.alsa-project.org/db/?f=b661fa1c8d2824b76db10b5cc4e20ebfab6b93aa
[10:05] <diwic> Saviq, ok, so in your case it does not detect the headset mic, although the hardware claims it should be able to.
[10:06] <cjwatson> mardy: it would be nice to get that far, but it isn't required.  I haven't worked out whether the files in the -dev package are multiarch-safe (any files in paths that are common between architectures must be bitwise-identical on all architectures)
[10:06] <cjwatson> mardy: let me have a quick look at that if you want
[10:06] <diwic> Saviq, at this point I think your best workaround is to use hdajackretask (in the alsa-tools-gui package) and remove jack detection for the headset mic pin
[10:07] <diwic> Saviq, that probably won't give you a dialog (I think...), but should enable you to manually select mic in sound settings
[10:08] <cjwatson> mardy: so, I *could*, but it would be futile; it depends on gir1.2-accounts-1.0, and /usr/lib/girepository-1.0/Accounts-1.0.typelib in that package has different contents on different architectures
[10:09] <cjwatson> mardy: since this isn't required to make "click chroot" work, I'd rather leave that problem for another day
[10:09] <cjwatson> (well, strictly, to make "apt-get install ubuntu-sdk-libs-dev:armhf" work)
[10:13] <cjwatson> mardy: by the way, I see there's a new upstream in trunk - is that planned to land for trusty, or should I be looking at doing a direct upload of this to the archive based on what's in trusty now?
[10:13] <Saviq> diwic, hmm indeed, got it to show up, but still no input (tried with an android/iOS ↔ nokia adapter, too, just to check)
[10:13] <mardy> cjwatson: thanks, I see there's little point in doing that
[10:14] <cjwatson> mardy: https://wiki.debian.org/Multiarch if you want background on multiarch, maybe https://wiki.debian.org/Multiarch/Implementation in particular
[10:14] <diwic> Saviq, ok, assuming you have increased the gain (it's quite low in your latest alsainfo) then maybe a hardware failure
[10:14] <Saviq> diwic, yeah, I up'ed it to 100%, no go
[10:15] <Saviq> diwic, so, I'll have to check if windoze let's me work with it, then, will do, thanks!
[10:15] <Saviq> lets
[10:15] <diwic> Saviq, ok!
[10:16] <mardy> cjwatson: I'd like to land the new version in trusty, yes. So I think we'll take care of landing it.
[10:16] <cjwatson> ok, great, thanks
[10:17] <cjwatson> Laney: are you likely to be able to land https://code.launchpad.net/~cjwatson/ubuntu-system-settings/arch-any/+merge/211426 today?  it's blocking several things in -proposed
[10:18] <Laney> cjwatson: Sure, I can do
[10:18] <mardy> dbarth: hi! Can you make https://code.launchpad.net/~cjwatson/libaccounts-glib/multiarch/+merge/211468 land?
[10:18] <Laney> seb128: ^ doing that on its own to unblock stuff, okay?
[10:19] <seb128> Laney, no, please wait
[10:19] <Laney> why?
[10:19] <seb128> Laney, I've some trivial changes for the wizard I want to include
[10:19] <Laney> could do another one ...
[10:19] <Laney> but okay, you do it
[10:19] <seb128> those can't bug anything, the wizard is not used
[10:19] <seb128> ok, sure
[10:19] <seb128> it just feels like we could batch them
[10:20] <seb128> but go ahead if you want, I can do another one later
[10:20] <seb128> cjwatson, just curious, how is u-s-s blocking things? it shouldn't have much rdepends
[10:20] <seb128> oh, I guess it's the online account panel needed it, and that one has rdepends
[10:21] <dbarth> mardy: hi
[10:21] <cjwatson> seb128: {clickmanager-plugin, ubuntu-purchase-service} -> ubuntuone-credentials -> ubuntu-system-settings-online-accounts -> ubuntu-system-settings
[10:22] <seb128> cjwatson, right, online-accounts, thanks ;-)
[10:22] <cjwatson> I mean it's all stuff nothing needs yet but I still want to keep the list short
[10:22] <seb128> right
[10:22] <seb128> Laney, well, your call, feel free to land it now if needed, I can put another landing in a few hours for the one things on the backlog
[10:22] <dbarth> mardy: will add to the silo
[10:23] <mardy> dbarth: thanks!
[10:23] <Laney> seb128: thanks, I will do so that proposed can clear out
[10:23] <seb128> Laney, thanks
[10:23] <dbarth> mardy: added line 13, along with the rest of the online accounts MPs
[10:23] <Laney> well, they are in firefighting mode again so you never know ...
[10:24] <dbarth> mardy: it's a no-op on desktop, but we will need to re-test on the phone with all of the recent changes
[10:25] <cjwatson> Laney: they're being fairly good about letting through obvious packaging adjustments, so far anyway
[10:25] <Laney> Yeah, but there's a new problem today in that the images don't boot, apparently. :P
[10:25]  * Laney goes to ask anyway
[10:28] <Laney> bah, I can't cross-build system-settings any more
[10:29] <Laney> http://paste.ubuntu.com/7113317/
[10:31] <seb128> qt5.2 regression?
[10:32] <Laney> sec
[10:41] <xnox> slangasek: bdmurray: updated app-install-data-ubuntu uploaded. But we also need updated "command-not-found" data, which is separate?! I'm not sure how that is generated.
[11:23] <zul> pitti: ack
[11:32] <Laney> ah I think it's the M-A: foreign on qt5-qmake
[11:33] <Laney> it now installs stuff in triplet-namespaced locations
[11:35] <Laney> http://anonscm.debian.org/gitweb/?p=pkg-kde/qt/qtbase.git;a=commitdiff;h=dd85a4c4d6eb19a01e75959d4725f7298b63b852;hp=c5a1ab594b27738adec10d346def2bc71b23f58f
[11:40] <cjwatson> Laney: yeah, I noticed the M-A: foreign seemed wonky given the paths
[11:44] <Laney> It looks like it could be made M-A: same
[11:46] <Laney> assuming the manpage compresses the same way, I guess
[11:46] <Laney> Mirv: ^ wdyt?
[11:48] <Mirv> Laney: looks like :same to me now that the mkspecs were moved
[11:49] <Mirv> MR:s welcome, there's one new qtbase upload being prepared in CI Train already
[11:50] <Laney> ok, if we check coinstallability explicitly
[11:57] <Laney> Mirv: how does it work with the source package?
[11:57] <Laney> do I add a changelog entry?
[11:57] <Laney> I'd expected to see stuff merged into the packaging branch but there is nothing there
[12:04] <Mirv> Laney: full changelog entry at all, propose against https://code.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtbase-opensource-src and CI will run tests and merge after top-approving
[12:04] <Mirv> s/at/and/
[12:05] <Mirv> at the same time, it can be uploaded to a landing PPA via CI Train, but it's not possible right now since qtbase is already being released via CI Train (ETA 1-2 hours)
[12:05] <Laney> ok
[12:07] <Mirv> Laney: so, umm, maybe merge in lp:~timo-jyrinki/kubuntu-packaging/qtbase_sync_from_archives_and_add_harfbuzz_patches first since it's likely to go in, and prepare ubuntu10 upload
[12:08] <Mirv> there was yet another upload by ricardo in the morning without CI involved
[12:12] <Laney> Mirv: ok, there it is & requested your review
[12:12] <Laney> let me know when it's up & built so that I can test it out
[12:18] <Mirv> Laney: thanks, I will
[12:30] <apachelogger> tseliot: bug 1291526  ... what I don't get, why would it run into an xioerror when prime selecting nvidia, but not when using intel?
[12:40] <Mirv> Laney: bzr is choking on your changelog entry, the time stamp is mangled (missing '0')
[12:40] <Laney> oops
[12:40] <Laney> it probably got damaged in the merge
[12:40] <Laney> there was a conflict of course
[12:41] <Laney> Mirv: try that
[12:41] <Mirv> works
[12:43] <Laney> Riddell: I'm getting reject emails from this merge proposal I just made
[12:44] <Laney> Can you maybe make them be discarded instead? Or better have a code review list where they are accepted
[12:44] <Riddell> Laney: from kubuntu-devel?
[12:44] <Laney> yes
[12:44] <Laney> I guess because kubuntu-packagers had a requested review
[12:47] <Riddell> Laney: unfortunately merge request have an implicit destination so I don't think there's a way to have mailman accept them automatically
[12:53] <Laney> Riddell: AFAICS the best you could do would be to add a spam filter for it
[12:54] <Laney> those can match any header
[12:54] <Laney> For example you could match on X-Launchpad-Message-Rationale: Reviewer @kubuntu-packagers
[13:29] <jamespage> I can't quite believe I've not had todo this before but what's the right way to move upstart configs between files at the same time as renaming them?
[13:30] <barry> cyphermox: an update and reboot seemed to bring back the global menu for claws at least.  not for emacs (but a menu bar is kind of an anathema for that anyway :)
[13:34] <cyphermox> barry: good :)
[13:59] <Mirv> release team acked bug #1207812 so if anyone ready for an upload please sponsor the branch I prepared during my patch pilot turn
[14:04] <seb128> Mirv, I can do that
[14:06] <Mirv> seb128: thanks.
[14:06] <seb128> Mirv, yw, thanks for working on the update ;-)
[14:10] <cjwatson> tjaalton: do you think you could sort out the libxmlrpc-c3-dev reverse-build-deps on http://people.canonical.com/~ubuntu-archive/nbs.html ?  I assume they need to be libxmlrpc-core-c3-dev now, but I don't really now
[14:10] <cjwatson> *know
[14:11] <cjwatson> tjaalton: (you can probably ignore tcos; it seems to have Build-Depends: libxmlrpc-c3-dev | libxmlrpc-core-c3-dev already)
[14:11] <tjaalton> cjwatson: okay
[14:11] <cjwatson> thanks
[14:11] <tjaalton> seems I missed the old names
[14:12] <tjaalton> although.. *cough* it failed to build on arm64/ppc64el
[14:12] <cjwatson> what did?
[14:12] <tjaalton> no wait
[14:12] <cjwatson> https://launchpad.net/ubuntu/+source/xmlrpc-c/1.33.06-0ubuntu1 looks fine
[14:12] <tjaalton> that got fixed by itself?
[14:12] <tjaalton> oh good
[14:12] <cjwatson> maybe it was transient
[14:13] <tjaalton> yeah it was weird
[14:13] <tjaalton> some test failed
[14:49] <tedg> slangasek, url-dispatcher didn't officially get added to the touch FFE, do you think we can add it?  bug 1208989
[15:01] <cjwatson> GunnarHj: mythes-sv is stuck in trusty-proposed because it builds uninstallable binaries on arm64 and ppc64el.  You'll probably end up with something similar in Debian.  Would it perhaps be worth an artificial build-dependency on libreoffice-dev (or something like that) so that you only build on the architectures that have libreoffice?
[15:02] <cjwatson> GunnarHj: Or maybe the binary package should be Architecture: all (which would avoid this problem)?  It doesn't seem to do anything in its build phase
[15:11] <Laney> cjwatson: Already fixed, see -2
[15:12] <cjwatson> Laney: oh right
[15:15] <pitti> cjwatson: right, I uploaded -2 to Debian, will sync once it gets imported
[15:16] <cjwatson> ta
[15:47] <Saviq> Mirv, xnox, bug #1294186, otherwise we'll never get it done...
[15:49] <Laney> Saviq: I have that fix building in a silo now
[15:49] <Laney> well, potential fix
[15:50] <Saviq> Laney, oh, great
[15:50] <Laney> we'll see, it might need extra fixes for looking up too
[15:51] <ritz> wtf, my precise boot up shows a debian logo on vm
[15:51] <ritz> when did this happen
[15:52] <heath> I'm wanting to write an app which utilizes the play/pause, prev, next, and volume buttons on my macbook. Tips on where to get started?
[15:53] <ritz> heath,  configure the shortcuts keys
[15:53] <ritz> why write an app ?
[15:53] <ritz> assuming linux understands the keys
[15:54] <Saviq> heath, they should be delivered to your app as XF86Audio* keys, see http://wiki.linuxquestions.org/wiki/XF86_keyboard_symbols
[15:55] <heath> ritz: If there are multiple running apps which utilize the media keys, which one has preference?
[15:55] <GunnarHj> cjwatson: Thanks for your head up re mythes-sv!
[15:55] <Saviq> heath, so yeah, for Ubuntu it's rather different, you need to connect to the sound indicator which takes the keys
[15:55] <cjwatson> Sorry it was a duplicate one
[15:56] <Saviq> heath, http://askubuntu.com/questions/7342/how-do-i-integrate-an-application-in-the-sound-menu-using-python should get you started
[15:57] <ritz> heath,  whichever you configure the shortcuts for
[15:57] <ritz> or write a script to be called upon multimedia keys
[15:57] <ritz> heath, http://askubuntu.com/questions/48393/how-to-make-the-keyboard-media-keys-to-work-with-vlc-globally
[16:03] <heath> That's a neat link ritz
[16:04] <heath> Saviq: I'll definitely be utilizing your link
[16:04] <heath> Thanks
[16:05]  * heath wonders if it's possible for a web app to connect to the sound indicator
[16:06] <heath> Hrm, if youtube can be integrated, then yes
[16:15] <hallyn> xnox: jodh: I went ahead and filed bug 1294200
[17:12] <Laney> Mirv: this is no good
[17:12] <Laney> It wans to reference an armhf uic
[17:33] <bdmurray> juliank: I've made uploaded another change to python-apt it seems slangasek and I missed a bit
[17:35] <juliank> bdmurray: Thanks for letting me know. I also have some patches in upstream git, I'll do a <IP_ADDRESS> release soon.
[17:36] <xnox> Laney: qmake doesn't know how to reference "built_arch" tools, cmake does.
[17:36] <xnox> Laney: that's a known bug I haven't fixed yet.
[17:36] <juliank> Bug fixes only of course (yes, I'm counting uncompressed data.tar support as a bug fix)
[17:36] <Laney> xnox: It is using cmake
[17:37] <juliank> bdmurray: It's a bit unfortunate to only have non-public errors.ubuntu.com resources in the changelog. I cannot seem them at all
[17:38] <juliank> The bug fix seems strange
[17:39] <xnox> Laney: oh.
[17:40] <bdmurray> juliank: here is the traceback http://pastebin.ubuntu.com/7115343/
[17:41] <Laney> xnox: Qt5WidgetsConfigExtras.cmake looks for host arch tools
[17:41] <Laney> Dunno how to fix that
[17:43] <juliank> bdmurray: I believe a better fix would be to change parse() to not generate bytes strings.
[17:43] <juliank> in self.comment
[17:45] <juliank> It looks like parse() was called with a bytes string (that is, not read using the SourcesList class). In such a case, we need to decode the line if it is not unicode already (once in __init__ and once in __parse__, to make sure)
[17:46] <xnox> Laney: in cmake itself, i added a whole bunch of overrides for all the tools to look for correct arch tools, when building under environment like the one exported by dpkg-architecture -aarmhf-c
[17:46] <xnox> Laney: maybe i need to fix/tweak those. Do you have an easy/simple reproducer for me to iterate with?
[17:46] <bdmurray> juliank: okay
[17:48] <Laney> xnox: landing-001 ppa, cross-build ubuntu-system-settings
[17:49] <Laney> xnox: I'm guessing you want a similar override to those cmake ones in this file then
[17:51] <juliank> bdmurray: This is still Python 2 code? It also crashes for me in another location in Python 3 with a simple test line in bytes.
[17:54] <xnox> Laney: i'll look into it.
[17:54] <xnox> Laney: probably not tonight though, need to finish on time today.
[17:54] <Laney> nm
[18:00] <juliank> bdmurray: Have you checked whether your fix actually work. I believe the problem is more that we now return a unicode object in __str__, causing it too fail afterwards because builtin str() tries to convert the unicode to str.
[18:01] <juliank> There's not much we can do about that, except for adding __unicode__ and changing the other code to use __unicode__ instead.
[18:01] <juliank> or using python 3 instead of 2.
[18:03] <Laney> xnox: oh, I added some rules which make it work
[18:03] <bdmurray> juliank: not that specific change no, I've had a hard time recreating this specific dist upgrade errors with sources list
[18:03] <xnox> Laney: cool, i'll probably will snitch them to keep cmake just working for all packages.
[18:04] <Laney> xnox: I added them to that MultiArchCross.cmake file
[18:04] <Laney> lemme get a diff
[18:04] <Laney> it just copies ones that are already there for some new tools
[18:04] <Laney> or newly-moved, what evs
[18:05] <juliank> bdmurray: I'm probably going to commit http://paste.debian.net/88436/ for this. It decodes byte strings to utf-8 and encodes the internal unicode to utf-8 if you call str() in Python 2 or bytes() in Python 3
[18:06] <juliank> It even has a test case for both bytes and unicode.
[18:07] <juliank> Not only that, it even contains a German word.
[18:09] <bdmurray> juliank: okay, great.
[18:12] <infinity> jodh: Any hope of my chroot-sessions bug being fixed pre-beta?
[18:13] <infinity> jodh: It's amazingly noisy on machines that set up and tear down chroots constantly (*cough*buildds*cough*)
[18:26] <Laney> xnox: bug #1294186 - please review the debdiff when you have time
[18:26] <juliank> bdmurray: Actually, instead of using unicode everywhere, even if not needed in python 2, how about simply opening the files in utf-8 in Python 3, and keeping the Python 2 code in bytes strings? I think this would work better, as that's the way we handle it everywhere else in the code.
[18:43] <juliank> bdmurray: I now (locally) reverted the unicode patch and added http://paste.debian.net/88438/ instead; which only forces utf-8 in Python 3.
[18:44] <juliank> It seems to work just fine in both Python 2 and 3 with the test case and has minimum impact.
[18:47] <juliank> We would not have those problems if people did not write files in an UTF-8 environment and then run reading code in a non-UTF-8 environment like C instead of C.UTF-8
[18:49] <juliank> apt_pkg.size_to_str() is broken in a non-unicode environment as well, BTW.
[19:09]  * juliank is waiting for his CI to start & complete
[19:50] <juliank> bdmurray: I have reverted the unicode change in upstream git for now. I'm not sure what I really want to do. Just hardcoding UTF-8 seems wrong. People might run in a non-UTF-8 locale, and things would break then. I have looked at the other code and we do not assume seem to assume UTF-8 for TagFile, but rather use the default encoding there as well (right, cjwatson?). I'd much prefer if code that sets a wrong locale like aptdaemon just gets f
[19:50] <juliank> ixed instead.
[19:50] <juliank> This way everyone can use the encoding they prefer.
[19:53] <juliank> Python 3 uses the LANG environment variable to determine file encoding.
[19:54] <bdmurray> juliank: it looks like the release upgrader sets the following - locale.setlocale(locale.LC_ALL, "")
[19:55] <juliank> Which just is the default encoding. But someone must set it to a non-unicode encoding before running it, otherwise things would not break.
[19:56] <juliank> locale.setlocale() seems to not influence the default encoding, BTW
[19:56] <juliank> It will determine that during startup AFAICT
[19:56] <juliank> It=Python 3
[22:55] <lamont> why is it that after I unlock my screen, it generally re-locks the first time?
[22:55] <UserError> lustre adds 10~ MB to kernel size
[22:57] <infinity> lamont: Because reasons.
[22:57] <infinity> lamont: There's already a bug (or three) filed about it.
[23:00] <lamont> infinity: cool
[23:27] <UserError> Why are there so many ARM platforms in the libsound2 package? It keeps growing with bloat.
[23:27] <UserError> ALSA-know is that ain't right
[23:28] <infinity> UserError: It's 204k of text files.
[23:29] <UserError> the /usr/share/alsa/ucm/ dir is complete trash
[23:30] <infinity> "complete trash".  Thanks for your input.
[23:30] <UserError> for x86 platforms
[23:30] <infinity> It's 204k of text files.
[23:30] <UserError> it doesn't belong
[23:30] <infinity> Also, it's 204k of text files.
[23:30] <UserError> it has existed for years
[23:30] <infinity> Your crusade, and the language used to fight it, aren't going to win you any friends.
[23:31] <UserError> I know, it really bytes
[23:36] <UserError> in 12.04 it was 120K. That is almost a +100% growth from LTS to LTS.
[23:37] <infinity> It's tiny either way.
[23:37] <UserError> also that means that writes are being used against NAND, SSD, and eMMC storage for 4k blocks
[23:38] <UserError> Now, multiply that by the number of devices and SSD servers that exist
[23:41] <infinity> You're making and argument for removing every package from the archive.
[23:41] <infinity> Wouldn't want to write to those precious disks and harm them.
[23:42] <UserError> and EC2 instances, Azure (copied from EC2) and OpenVZ appliance (proxmox too)
[23:42] <UserError> I understand why certain things are there for supporting hardware. I do not understand files there for impossible reasons.
[23:42] <infinity> None of those should have libasound2 installed in the first place.
[23:42] <infinity> The simple answer to your question is because it's an arch:all package, and includes support for *drum roll* all arches.
[23:43] <infinity> And, curiously, ARM seems to be the only arch that leverages UCM sanely, so it's the only one that ships a bunch of (tiny) UCM profiles.
[23:43] <UserError> and yet the container profile for ubuntu minimal VM still has plenty of modules that shouldn't be there
[23:43] <UserError> I agree there.


[02:25] <kc2bez[m]> wxl: did you see bug 1916356 ?
[02:27] <kc2bez[m]> I think it is directly related to https://github.com/calamares/calamares/issues/1637
[02:28] <kc2bez[m]> Which isn't really a calamares bug
[02:28] <kc2bez[m]> I am not sure how to adjust the LP bug
[02:34] <kc2bez[m]> Basically we need this commit for kpmcore https://invent.kde.org/stikonas/kpmcore/-/commit/36dfae351ffac48134e2697b4fc1024e7557e319
[06:31] -lugito:#lubuntu-devel- [Lubuntu CI] jobgenerator just succeeded after failing: https://ci.lubuntu.me/job/jobgenerator/882/
[06:31] -lugito:#lubuntu-devel- [Lubuntu CI] merger_libqtxdg FAILURE: https://ci.lubuntu.me/job/merger_libqtxdg/731/
[06:31] -lugito:#lubuntu-devel- [Lubuntu CI] merger_libfm-qt FAILURE: https://ci.lubuntu.me/job/merger_libfm-qt/756/
[06:43] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/372/
[06:43] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/372/
[06:43] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/119/
[06:43] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/620/
[06:43] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/620/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/120/
[08:49] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/620/
[11:05] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lximage-qt just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lximage-qt/110/
[11:26] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-notificationd just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-notificationd/112/
[11:26] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-notificationd just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-notificationd/112/
[11:26] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pcmanfm-qt just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_pcmanfm-qt/385/
[11:36] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt just became unstable: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/117/
[12:02] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_nm-tray just became unstable: https://ci.lubuntu.me/job/hirsute_stable_nm-tray/108/
[12:33] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/605/
[12:48] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-session just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-session/112/
[12:48] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab just became unstable: https://ci.lubuntu.me/job/hirsute_stable_screengrab/111/
[12:48] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/383/
[12:48] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/605/
[12:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/112/
[13:13] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_compton-conf just became unstable: https://ci.lubuntu.me/job/hirsute_stable_compton-conf/113/
[13:13] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/606/
[13:14] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_liblxqt/384/
[13:14] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_liblxqt/113/
[13:39] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/694/
[13:39] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libsysstat just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_libsysstat/589/
[13:40] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-config just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-config/108/
[13:40] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-config just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-config/108/
[13:40] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-config/694/
[13:55] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_libsysstat just became unstable: https://ci.lubuntu.me/job/hirsute_stable_libsysstat/117/
[14:02] <The_LoudSpeaker> quick query: if I put a package in a ppa, while building, will it use proposed? coz the dependencies are in proposed.
[14:06] <The_LoudSpeaker> also, latest debian policy is 4.5.1 ?
[14:07] <The_LoudSpeaker> i left it at 4.5.0 for all packages till now.
[14:07] <The_LoudSpeaker> 🤦
[14:07]  * The_LoudSpeaker facepalms
[14:08] <RikMills> The_LoudSpeaker: a ppa will only use packages from proposed if you change its settings to allow that, in the 'Edit PPA dependencies' link
[14:21] <The_LoudSpeaker> oh. thanks!
[14:23] <The_LoudSpeaker> also, obconf-qt not in lubuntu packageset?
[14:23] <The_LoudSpeaker> my upload got rejected
[14:24] <The_LoudSpeaker> "The signer of this package is lacking the upload rights for the source package, component or package set in question."
[14:25] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libsysstat just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_libsysstat/589/
[14:28] <RikMills> $ ubuntu-upload-permission -a obconf-qt
[14:28] <RikMills> All upload permissions for obconf-qt:
[14:28] <RikMills> Component (universe)
[14:28] <RikMills> [14:28] <RikMills> * MOTU (motu) [team]
[14:28] <The_LoudSpeaker> are you MOTU RikMills ?
[14:29] <RikMills> yes
[14:29] <The_LoudSpeaker> Would you mind uploading this package? I can send a patch which you just git apply and then debuild -S -sa and upload.
[14:30] <RikMills> I can have a look at least
[14:34] <The_LoudSpeaker> https://paste.ubuntu.com/p/qTY84QY47W/
[14:34] <The_LoudSpeaker> ^ RikMills
[14:35] <The_LoudSpeaker> same for qtermwidget too.
[14:36] <The_LoudSpeaker> is there a gui / web tool to check the upload permissions? everytime I run ubuntu-upload-permission form my lxc container, it asks for authenication from browser.
[14:36]  * The_LoudSpeaker goes to read the requirements for MOTU
[14:38] <The_LoudSpeaker> I will arc diff those which I cannot upload, someone wil have to sponsor it.
[14:38] <The_LoudSpeaker> cc: wxl kc2bez[m] tsimonq2
[14:40] <RikMills> error: patch failed: debian/changelog:179
[14:40] <RikMills> error: debian/changelog: patch does not apply
[14:40] <RikMills> error: patch failed: debian/copyright:8
[14:40] <RikMills> error: debian/copyright: patch does not apply
[14:42] <kc2bez[m]> The_LoudSpeaker: https://people.canonical.com/~ubuntu-archive/packagesets/hirsute/lubuntu
[14:43] <The_LoudSpeaker>  RikMills lite, I will arc diff.
[14:43] <RikMills> don't run it from a container
[14:43] <The_LoudSpeaker> kc2bez[m]: yeah I saw that page and obconf-qt isn't there.
[14:44] <kc2bez[m]> neither is qtermwidget or qterminal
[14:45] <RikMills> you should add these to your supported seed and ask for an update
[14:46] <The_LoudSpeaker> https://phab.lubuntu.me/D106
[14:46] -lugito:#lubuntu-devel- [Needs Review] New upstream version: https://phab.lubuntu.me/D106
[14:46] <RikMills> there are a lot I should do for kubuntu, but keep forgetting as MOTU means I can upload anyway **whoops**
[14:47] <kc2bez[m]> Yeah, I think it has been the same for Simon.
[14:47] <The_LoudSpeaker> qtermwidget has a bunch of stuff in symbols file. I am not sure if I can correct all of it. creating a diff now.
[14:53] <RikMills> The_LoudSpeaker: https://launchpad.net/ubuntu/+source/obconf-qt/0.16.0-1ubuntu1
[14:57] <The_LoudSpeaker>  Thenks! :D
[14:57] <RikMills> are you going to get all these merges done before feature freeze on Thursday?
[14:58] <The_LoudSpeaker> trying to.
[14:59] <RikMills> well, shout later in the week if you might fall short
[14:59] <RikMills> I don't mind doing a few to help
[15:00] <The_LoudSpeaker> sure. I do have some other assignments lined up.
[15:06] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-about just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-about/113/
[15:11] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-admin just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-admin/111/
[15:27] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/595/
[15:32] <The_LoudSpeaker> RikMills: https://phab.lubuntu.me/D107
[15:32] -lugito:#lubuntu-devel- [Needs Review] New upstream version.: https://phab.lubuntu.me/D107
[15:33] <The_LoudSpeaker> also, you didn't  commit obconf on phab right? only uploaded to archive.
[15:33] <The_LoudSpeaker> I will push it.
[15:34] -lugito:#lubuntu-devel- [rOBCONFQTPACKAGINGaa2ae9dafcb8: New upstream version] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rOBCONFQTPACKAGINGaa2ae9dafcb8
[15:34] <RikMills> well, it's your commit :P
[15:35] <RikMills> does qtermwidget build on all arches?
[15:35] <The_LoudSpeaker> if you are uploading qtermwidget, please add it to a ppa with proposed enabled.
[15:36] <The_LoudSpeaker> one sec let me check
[15:36] <RikMills> I'll put it in a bileto ppa to test
[15:36] <The_LoudSpeaker> arch=any
[15:36] <The_LoudSpeaker> according to control file.
[15:36] <The_LoudSpeaker> and only amd64 is doubtful actually.
[15:37] <The_LoudSpeaker> paste the ppa link here once you upload.
[15:45] <RikMills> The_LoudSpeaker: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3997/+sourcepub/12157706/+listing-archive-extra
[15:47] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/371/
[15:47] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/247/
[15:49] <The_LoudSpeaker> yay amd64 built fine. :)
[15:52] <RikMills> I'll let riscv64 finish
[15:56] <The_LoudSpeaker> yup.
[15:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/543/
[16:12] <RikMills> The_LoudSpeaker: https://launchpad.net/ubuntu/+source/qtermwidget/0.16.1-1ubuntu1
[16:13] <The_LoudSpeaker> Just as I was typing "push it"
[16:13] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/247/
[16:14] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-archiver UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-archiver/372/
[16:14] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/595/
[16:38] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/543/
[16:39] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/320/
[17:10] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/106/
[17:10] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-build-tools/107/
[17:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/focal_stable_lxqt-build-tools/544/
[17:11] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-openssh-askpass just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-openssh-askpass/114/
[17:14] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-globalkeys just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-globalkeys/112/
[17:23] <The_LoudSpeaker> i have lxqt-admin building fine in a ppa but failing in archives.
[17:23] <The_LoudSpeaker> https://launchpad.net/ubuntu/+source/lxqt-admin/0.16.0-1ubuntu1/+build/21063503
[17:23] <The_LoudSpeaker> https://launchpad.net/~theloudspeaker/+archive/ubuntu/devel-packages/+build/21063405
[17:26] <The_LoudSpeaker> something I missed here? says failed due to missing dependencies.
[17:26] <The_LoudSpeaker> archives don't build using proposed? ppa has proposed as dependency.
 auto-sync should have just happened, so likely something synced and building has temporarily make build deps unistallable in -proposed
[17:28] <The_LoudSpeaker> okay. what do I do then? retry the build?
 wait for an hour or so, then retry
[17:30] <theloudspeaker> sare.
[17:35] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-build-tools UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_lxqt-build-tools/321/
[17:38] <RikMills> theloudspeaker: aha. it was due to new python3.9 migrating from -proposed to -release. When something migrates, you can have a short period when neither the old or the new version is available
[17:38] <RikMills> one of those odd things
[17:39] <kc2bez[m]> Timing is everything.
[17:39] <RikMills> this was BAD timing :P
[17:39] <kc2bez[m]> Yes :D
[17:42] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-policykit just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-policykit/114/
[17:47] <The_LoudSpeaker> Ah. Okay.
[17:48] <The_LoudSpeaker> I will retry the build once I get back home.
[17:48] <The_LoudSpeaker> Came out to the railway station to bid farewell to a friend.
[18:32] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-panel just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_lxqt-panel/373/
[18:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-sudo just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-sudo/112/
[18:58] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/633/
[18:58] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/149/
[19:10] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-sudo just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-sudo/112/
[19:24] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/633/
[19:24] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/395/
[19:27] <wxl[m]> <kc2bez[m] "Basically we need this commit fo"> Did you test it as a patch? Other options are to downgrade dosfstools or wait until March
[19:28] <kc2bez[m]> I have not tested it myself, no. I am not sure I have an EFI machine to test it on.
[19:29] <RikMills> March for what?
 @wxl @kc2bez Have EFI machine avail - can I test that?
[19:35] <wxl[m]> <kc2bez[m] "I have not tested it myself, no."> You can run vbox as efi
[19:35] <kc2bez[m]> Good point,
[19:35] <kc2bez[m]> I will try to test that later
[19:36] <wxl[m]> <RikMills "March for what?"> According to upstream, the next KDE release. Probably a bad option
[19:40] <RikMills> wxl[m]: the release is April 22nd
[19:40] <RikMills> unless you mean the beta
[19:40] <RikMills> or they did
[19:42] <RikMills> https://community.kde.org/Schedules/release_service/21.04_Release_Schedule
[19:43] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/149/
[19:43] <RikMills> ^ I must fix that!
[19:44] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/395/
[19:45] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/633/
[19:48] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_qterminal/131/
[19:48] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_qterminal/131/
[19:49] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_qterminal/895/
[19:50] <The_LoudSpeaker> we still need this right? https://phab.lubuntu.me/source/lxqt-session/browse/ubuntu%252Fhirsute/debian/patches/ensure-necessary-paths-are-pulled-from.patch
[19:50] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_qterminal/895/
[19:50] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qterminal/435/
[19:51] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qterminal/435/
[19:51] -lugito:#lubuntu-devel- [rPAVUCONTROLQTPACKAGING5784bf15c68f: restore correct upstream signing key] rikmills (Rik Mills) committed: https://phab.lubuntu.me/rPAVUCONTROLQTPACKAGING5784bf15c68f
[19:51] -lugito:#lubuntu-devel- [rPAVUCONTROLQTPACKAGING9662277ed94e: release to hirsute] rikmills (Rik Mills) committed: https://phab.lubuntu.me/rPAVUCONTROLQTPACKAGING9662277ed94e
[19:53] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/354/
[19:55] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/638/
[19:55] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/142/
[19:55] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/395/
[20:09] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget just failed after succeeding: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/354/
[20:10] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/621/
[20:15] <wxl[m]> <The_LoudSpeaker "we still need this right? https:"> Yep
[20:19] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/621/
[20:20] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/373/
[20:21] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/639/
[20:21] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/143/
[20:25] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/396/
[20:27] <The_LoudSpeaker> https://phab.lubuntu.me/D108
[20:27] -lugito:#lubuntu-devel- [Needs Review] New upstream version.: https://phab.lubuntu.me/D108
[20:27] <The_LoudSpeaker> ^ wxl[m]
[20:33] <The_LoudSpeaker> err.
[20:34] <kc2bez[m]> yeah
[20:34] <The_LoudSpeaker> pcmanfm-qt and lxqt-sudo got -1ubuntu2 instead of -1ubuntu1
[20:34] <The_LoudSpeaker> kc2bez[m]: you noticed this? ^
[20:34] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/373/
[20:34] <RikMills> why ubuntu2?
[20:35] <kc2bez[m]> no, didn't they get a rebuild from the permissions issue
[20:35] <kc2bez[m]> look at the changelog
[20:35] <The_LoudSpeaker> RikMills: i did dch -i on top of changelog I got from MoM
[20:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/120/
[20:35] <RikMills> well don't!
[20:36] <The_LoudSpeaker> RikMills: yeah. noticed on next package.
[20:36] <The_LoudSpeaker> kc2bez[m]: I didn't get a notif about rebuild.
[20:36] <The_LoudSpeaker> got a accepted mail for both.
[20:36] <kc2bez[m]> look at what is in the archive first The_LoudSpeaker:
[20:36] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/121/
[20:37] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-notificationd just became unstable: https://ci.lubuntu.me/job/hirsute_stable_lxqt-notificationd/112/
[20:37] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pcmanfm-qt just became unstable: https://ci.lubuntu.me/job/hirsute_stable_pcmanfm-qt/117/
[20:38] <RikMills> ubuntu2 won't get rejected, but it is very confusing
[20:38] <RikMills> especially if someone wants to check the history and can't find a ubuntu1
[20:38] <The_LoudSpeaker> kc2bez[m]: https://launchpad.net/ubuntu/+source/lxqt-sudo/0.16.0-1ubuntu2
[20:38] <The_LoudSpeaker> it is still buolding?
[20:38] <The_LoudSpeaker> RikMills: yeah. my bad. How do I fix it now?
[20:39] <The_LoudSpeaker> *building
[20:39] <kc2bez[m]> You can't go backwards
[20:39] <RikMills> no point now
[20:39] <The_LoudSpeaker> sorry.
[20:39] <RikMills> as ubuntu2 is burnded
[20:39] <RikMills> *burned
[20:39] <RikMills> there are WORSE mistakes :)
[20:39] <The_LoudSpeaker> I put it in ppa befoere this. didn't notice there too. *facepalms*
[20:40]  * The_LoudSpeaker is coffee deprived
[20:40]  * kc2bez[m] slides The_LoudSpeaker: a grande sized coffee
[20:41]  * The_LoudSpeaker quickly gulps it in one go. spilling some on his t shirt.
[20:42] <The_LoudSpeaker> btw, side quest: has latest thunderbird arrived in focal yet?
[20:44] <The_LoudSpeaker> wxl[m]:  kc2bez[m] RikMills don't land the qteerminal diff yet. bumped the version number there too.
[20:44] <kc2bez[m]> You have some other changes needed too, I marked it up.
[20:44] <RikMills> that is the one I saw
[20:46] <The_LoudSpeaker> kc2bez[m]: Ack.
[20:50] <The_LoudSpeaker> kc2bez[m]: also, it is really neccessary to put "merge from debian unstable" ? "new upstream version should suffice right? as debian is an upstream for us.
[20:51]  * The_LoudSpeaker has not put "merge from debian unstable" in a lot of uploads today.
[20:51]  * The_LoudSpeaker hides
[20:51] <kc2bez[m]> I think the merge notation is preferred
[20:52] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/596/
[20:55] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pcmanfm-qt just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_pcmanfm-qt/386/
[20:57] <The_LoudSpeaker> kc2bez[m]: Ack. will add going forward.
[20:57] <kc2bez[m]> Thanks, sounds good.
[21:05] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_screengrab just became unstable: https://ci.lubuntu.me/job/hirsute_stable_screengrab/111/
[21:07] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-config just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_lxqt-config/695/
[21:08] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_libsysstat just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_libsysstat/590/
[21:08] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/248/
[21:09] <RikMills> The_LoudSpeaker: are you going to push changes for qtermwidget and your other uploads?
[21:11] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_liblxqt UNSTABLE: https://ci.lubuntu.me/job/focal_stable_liblxqt/606/
[21:23] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_obconf-qt just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_obconf-qt/599/
[21:27] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_obconf-qt just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_obconf-qt/599/
[21:36] <The_LoudSpeaker> yeah.
[21:36] <The_LoudSpeaker> in a while.
[21:36] <The_LoudSpeaker> ^ RikMills
[21:37] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_qterminal/895/
[21:39] -lugito:#lubuntu-devel- [rQTERMWIDGETPACKAGING8b09fbf3e1bd: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rQTERMWIDGETPACKAGING8b09fbf3e1bd
[21:40] -lugito:#lubuntu-devel- [rLXIMAGEQTPACKAGING3b083da2d89e: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXIMAGEQTPACKAGING3b083da2d89e
[21:40] <RikMills> thx
[21:41] -lugito:#lubuntu-devel- [rLXQTABOUTPACKAGING6727484617bb: New upstream version] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTABOUTPACKAGING6727484617bb
[21:42] -lugito:#lubuntu-devel- [rLXQTADMINPACKAGINGf73cf65ed651: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTADMINPACKAGINGf73cf65ed651
[21:43] -lugito:#lubuntu-devel- [rLXQTCONFIGPACKAGINGe522e9d2040f: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTCONFIGPACKAGINGe522e9d2040f
[21:43] -lugito:#lubuntu-devel- [rLXQTGLOBALKEYSPACKAGINGd4c426575b8d: New upstream version] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTGLOBALKEYSPACKAGINGd4c426575b8d
[21:44] -lugito:#lubuntu-devel- [rLXQTNOTIFICATIONDPACKAGINGdd6315e3e14b: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTNOTIFICATIONDPACKAGINGdd6315e3e14b
[21:45] -lugito:#lubuntu-devel- [rLXQTOPENSSHASKPASSPACKAGING83b8da643cda: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTOPENSSHASKPASSPACKAGING83b8da643cda
[21:45] -lugito:#lubuntu-devel- [rLXQTPOLICYKITPACKAGING8fc03f2ce45c: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTPOLICYKITPACKAGING8fc03f2ce45c
[21:46] -lugito:#lubuntu-devel- [rLXQTSESSIONPACKAGING35853fd3073b: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTSESSIONPACKAGING35853fd3073b
[21:47] -lugito:#lubuntu-devel- [rLXQTSUDOPACKAGINGa9b4deae18ac: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTSUDOPACKAGINGa9b4deae18ac
[21:47] -lugito:#lubuntu-devel- [rPCMANFMQTPACKAGING82d4ef5652f9: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rPCMANFMQTPACKAGING82d4ef5652f9
[21:48] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-sudo just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_lxqt-sudo/113/
[21:50] -lugito:#lubuntu-devel- [rLXQTPOWERMANAGEMENTPACKAGING5929b137ba36: New upstream version] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTPOWERMANAGEMENTPACKAGING5929b137ba36
[21:50] -lugito:#lubuntu-devel- [rLXQTRUNNERPACKAGING1e9e8523f042: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTRUNNERPACKAGING1e9e8523f042
[21:52] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-panel FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-panel/374/
[21:52] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qterminal FAILURE: https://ci.lubuntu.me/job/hirsute_stable_qterminal/131/
[22:01] -lugito:#lubuntu-devel- [rLXQTPANELPACKAGING2d271d3ad882: New upstream version.] The_LoudSpeaker (Raman Sarda) committed: https://phab.lubuntu.me/rLXQTPANELPACKAGING2d271d3ad882
[22:04] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal FAILURE: https://ci.lubuntu.me/job/groovy_stable_qterminal/436/
[22:04] <The_LoudSpeaker> kc2bez[m]: can you upload qterminal?
[22:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_qterminal/896/
[22:04] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal FAILURE: https://ci.lubuntu.me/job/groovy_stable_qterminal/436/
[22:04] <The_LoudSpeaker> and commit to phab too?
[22:04] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/639/
[22:05] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/143/
[22:05] <kc2bez[m]> <The_LoudSpeaker "kc2bez: can you upload qterminal"> I cannot, i have the same upload permissions as you.
[22:05] <The_LoudSpeaker> then  @RikMills bhaiya help us please.
 does everyone forget i'm a coredev lol?  😆
[22:05] <The_LoudSpeaker> we forget you exist.  I see different versions on phab and in archives.
[22:09] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_qterminal/896/
[22:10] <The_LoudSpeaker> Also, RikMills if you can do the upload of qterminal rn, it would be very helpful. solves almost all of lxqt 0.16 merge.
[22:10] <kc2bez[m]> <The_LoudSpeaker "@teward001 there's something int"> We need to sync what is in the archive with phab, it probably had a autosync with Debian
[22:11] <The_LoudSpeaker> kc2bez[m]: ohh. update on the task once that's done ploxx.
[22:12] <The_LoudSpeaker> only lxqt-panel is on dependency wait now. everything else is fine.
[22:12] <kc2bez[m]> I will give it a look in a few and let you know
[22:12] <The_LoudSpeaker> and since I uploaded it to archives, the dependency wait ones will be auto retried to build tomorrow right?
[22:13] <The_LoudSpeaker> if yes, then I am done, lxqt 0.16 merged.
[22:14] <The_LoudSpeaker> wxl[m]: WHERE ARE YOU? old man wake up and test all of it.
[22:15] <RikMills> The_LoudSpeaker: lxqt-archiver - looks like Simon got it ready to upload as a new source, did that in cosmic, and for whatever reason it was rejected
[22:16] <RikMills> now it has come through as a new source from debian
 https://launchpad.net/ubuntu/+source/lxqt-archiver
[22:16] <RikMills> with obviously much higher version
 and it's FTBFS
 RikMills: it's also FTBFS so you and Lubuntu team will want to dig
 Only because it need 0.16 libft-qt to build, which was not here yet (re @teward001: and it's FTBFS)
[22:18] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget FAILURE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/354/
 i can retry it
 and debian didn't version the build depends. sigh....
 RikMills: I'll push an update in then with a build dependency if you want
[22:18] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/622/
 because I need to retrigger the build anyways
 what's the min dependency?  >= 0.16?
 Could not find a configuration file for package "fm-qt" that is compatible
   with requested version "0.16.0".
 so that's a yes.
 >= 0.16.0
 indeed
[22:19] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/396/
[22:19] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget FAILURE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/355/
[22:19] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/focal_stable_lxqt-qtplugin/622/
 libfm-qt-dev (>= 0.16.0)  <— adding to it and uploading.
 The ubuntu delta will also stop the autosync, which is probably wise
 yep
 test building locally before i upload
 but then I'll push the changes to the repository
[22:23] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/634/
[22:23] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/150/
 (that's my standard workflow, as long as it doesn't FTBFS locally in sbuild I push xD)
 that said
 Phab'll need updated/merged after this
 but the ubuntu1 suffix WILL stop autosync and require merges
 which will prevent this kind of chaos going forward with things autosuperseding
 um, hmm interesting
 Rik: still FTBFS
 another part of lxqt not updated yet?
 let me dump logs
 https://paste.ubuntu.com/p/cck4SghPPn/
 is it libsysstat?
 it's failing during the actual build steps
 i'll let you dissect the logs
 BUT this is not uploaded yet - has the versioned dep though
 oh INTERESTING
 CMake Error at CMakeLists.txt:30 (find_package):
   Could not find a configuration file for package "fm-qt" that is compatible
   with requested version "0.16.0".
 so it sounds like there's still something going on there
 even with 0.16.0
 the dep is >= 0.16.0 and we know that dependency is present, is this an fm-qt bug maybe?
 > /usr/share/cmake/fm-qt/fm-qt-config.cmake, version: 0.15.1
 *checks something*
 ahhhhhhhhhh that's why
 it's stuck in proposed
 Yeah.
 and hasn't left yet
 let me enable proposed in my buildd
 With today's changes for pcmanfm and lximage, etc. It should get out of proposed soon.
[22:28] <kc2bez[m]> hot newness
 @guiverc will have a lot of testing to do when this lands. XD
 default 7d age unless blocked (re @The_LoudSpeaker: With today's changes for pcmanfm and lximage, etc. It should get out of proposed soon.)
 *checks the blocks*
 ouchies.  i assume pcmanfm is fixed?  https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libfm-qt
 removing libfm-qt7/0.15.1-0ubuntu5/amd64 from testing makes pcmanfm-qt/0.15.0-0ubuntu1/amd64 uninstallable
 build success though with proposed
 needed pcmanfm-qt 0.16 built against it, which was done 1 hr ago (re @teward001: it's stuck in proposed)
 that makes sense
 i'm going to push the update since it succeeds with Proposed enabled
 so will hopefully migrate soon
 It got fixed an hour ago. (re @teward001: ouchies.  i assume pcmanfm is fixed?  https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#libfm-qt)
 @The_LoudSpeaker @RikMills then it'll take a few hours for update_excuses and autopkgtests to run
 and then there's still the 7 day ageout period for proposed
 Yeah. Thought so. (re @teward001: @The_LoudSpeaker @RikMills then it'll take a few hours for update_excuses and autopkgtests to run)
 Nope. We are not debian (re @teward001: and then there's still the 7 day ageout period for proposed)
 you're right i'm thinking SRU ageouts :P (re @RikMills: Nope. We are not debian)
 lxqt-archiver changes uploaded with ubuntu1
[22:33] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/374/
 Thanks! Please update the task on phab too. That's the only thing to tick off the list.
[22:33] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-qtplugin/374/
 Apart from qterminal.
 Which @RikMills will upload soon i assume.
 britney is still taking ~5hrs per run, even with glibc migrated the other day!
 :(
[22:35] -lugito:#lubuntu-devel- [T185: deal with merges] teward (Thomas Ward) commented on the task: https://phab.lubuntu.me/T185#4253
[22:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/122/
 @The_LoudSpeaker i can't do the phab merge
[22:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-qtplugin FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-qtplugin/122/
[22:35] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-archiver/597/
 but i made a note in the task
[22:35] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-archiver FAILURE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-archiver/249/
[22:36] <The_LoudSpeaker> Thanks!
 yep.
[22:38] <The_LoudSpeaker> @RikMills: please upload and commit qterminal on phab and note on the task whenever it gets done.
 my note is that i uploaded the newer version so the 0.3.0-2ubuntu1 version will need to be merged into the Phab versions.
 other than that, it should build in proposed now :P
[22:38] <The_LoudSpeaker> teward: yeah. That's understood.
[22:39] <teward> perfect
[22:39] <teward> coffee run brb
[22:39]  * The_LoudSpeaker goes to sleep
[22:40] <guiverc> I'll love it when 0.16 lands, hopefully won't have to re-orient my displays every login :)  though kgiii has covered most of this cycle's testing; and @leokolb most QA-test installs too.  @The_LoudSpeaker
[22:42] <kgiii> I might get a couple of days off before it's time to start checking 21.10!
[22:42] -lugito:#lubuntu-devel- [rQTERMINALPACKAGING9d90f4c7add3: release to hirsute] rikmills (Rik Mills) committed: https://phab.lubuntu.me/rQTERMINALPACKAGING9d90f4c7add3
[22:42] -lugito:#lubuntu-devel- [rQTERMINALPACKAGING86cd9462e1a3: Merge branch 'ci/stable' into ci/unstable] rikmills (Rik Mills) committed: https://phab.lubuntu.me/rQTERMINALPACKAGING86cd9462e1a3
 done (re @lubuntu_bot: (irc) <The_LoudSpeaker> @RikMills: please upload and commit qterminal on phab and note on the task whenever it gets done.)
 wait. what task?
 :D
[22:44] -lugito:#lubuntu-devel- [T185: deal with merges] rikmills (Rik Mills) commented on the task: https://phab.lubuntu.me/T185#4256
 found the task. done also
[22:45] <kc2bez[m]> Thanks @RikMills and @teward001
[22:46] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_qterminal/132/
[22:46] <RikMills> screengrab and qps being done?
[22:46] <kc2bez[m]> They need to be
[22:47] <RikMills> both in your packageset, so cool
[22:48] <kc2bez[m]> 𝖜𝖝𝖑: I rebuilt kpmcore with that patch and it still fails I probably need to recompile cala against the updated kpmcore so I might have to build that in a ppa or something.
[22:48] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_obconf-qt just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_obconf-qt/600/
[22:48] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_qterminal just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_qterminal/896/
[22:48] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_obconf-qt just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_obconf-qt/600/
[22:48] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/focal_stable_sddm/639/
[22:48] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_sddm/143/
[22:49] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_sddm UNSTABLE: https://ci.lubuntu.me/job/groovy_stable_sddm/396/
[22:50] <RikMills> have upstream confirms that that patch is sufficient? when things say 'initial support' I often doubt
[22:50] <kc2bez[m]> I am not sure
[22:52] <kc2bez[m]> Gecko downgraded dosfstools to get it out the door
[22:53] <kc2bez[m]> It looks like the "Arches" got it working though
[22:59] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/634/
[22:59] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-panel FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-panel/375/
 hey look at that, the build successes there are BEAUTIFUL!  https://launchpad.net/ubuntu/+source/lxqt-archiver/0.3.0-2ubuntu1
[23:00] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt FAILURE: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/396/
[23:01] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_pavucontrol-qt just succeeded after failing: https://ci.lubuntu.me/job/hirsute_stable_pavucontrol-qt/150/
[23:01] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal FAILURE: https://ci.lubuntu.me/job/groovy_stable_qterminal/437/
[23:01] <kc2bez[m]> Yeah, awesome.
[23:01] <teward> yep, hope you don't mind the occasional prod by me on things ;)
[23:02] <kc2bez[m]> No it is appreciated, thanks.
[23:02] <teward> yep.
[23:04] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qterminal FAILURE: https://ci.lubuntu.me/job/groovy_stable_qterminal/437/
[23:05] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_pavucontrol-qt just succeeded after failing: https://ci.lubuntu.me/job/focal_stable_pavucontrol-qt/634/
[23:08] <teward> RikMills: The_LoudSpeaker: once either of you merge down the changes from upstream to phab for lxqt-archiver then either someone from your team or myself can upload it again if there's any Lubuntu changes you all need added
[23:09] <teward> unless as is is fine in which case yay no more autosyncs xD
 /me is not in lubuntu team
 you're listed as a developer here so ;)
 Implied
 I guess you lot may want to 'lubuntify' it
 technically i'm not on the lubuntu team either, but i'm considered part of it :P
 (Most of what i do is behind the scenes, keeping Phab and stuff working, testing RPi 400 and prepping a prebuilt image, etc. for it.)
 I am? (re @teward001: you're listed as a developer here so ;))
 Simon!
[23:12] <kc2bez[m]> LoL
 lol that's the title you get
 wish I had a title >Chaotic Sysop From Hell< lol
 Oh, this is a TG title?
[23:14] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget FAILURE: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/355/
 gotcha
[23:15] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_pavucontrol-qt just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_pavucontrol-qt/397/
[23:15] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_qtermwidget just succeeded after failing: https://ci.lubuntu.me/job/groovy_stable_qtermwidget/356/
 yep
 it's a TG title
 technically i'm in the LUbuntu Devel Team now because i help check merges, uploads, etc. but :P
 I can't see it, so did not know
 no worries :)
[23:23] -lugito:#lubuntu-devel- [T180: Cleanup Ubuntu Wiki] guiverc (Chris Guiver) commented on the task: https://phab.lubuntu.me/T180#4258
[23:28] -lugito:#lubuntu-devel- [T196: List of items on current wiki that ideally should exist on our current infrastructure] guiverc (Chris Guiver) just created this task: https://phab.lubuntu.me/T196
[23:31] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-about UNSTABLE: https://ci.lubuntu.me/job/hirsute_stable_lxqt-about/113/
[23:31] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-panel just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-panel/612/
[23:45] -lugito:#lubuntu-devel- [Lubuntu CI] focal_stable_lxqt-panel just failed after succeeding: https://ci.lubuntu.me/job/focal_stable_lxqt-panel/612/
[23:47] -lugito:#lubuntu-devel- [Lubuntu CI] groovy_stable_lxqt-panel FAILURE: https://ci.lubuntu.me/job/groovy_stable_lxqt-panel/375/
[23:47] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-panel just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-panel/116/
[23:47] -lugito:#lubuntu-devel- [Lubuntu CI] hirsute_stable_lxqt-panel just failed after succeeding: https://ci.lubuntu.me/job/hirsute_stable_lxqt-panel/116/