[00:13] <cwayne> mhall119: ping
[00:17] <mhall119> cwayne: pong
[00:18] <cwayne> mhall119: does an app need to explictly set its background as Theme.Palette.normal.background to have it's background change when the default theme is changed?
[00:18] <mhall119> um.....I don't know
[00:18] <mhall119> Kaleo might
[00:19] <imnichol> mhall119, since you're already here, and you know what you're talking about: is there documentation on using the camera in qml?
[00:19] <mhall119> imnichol: well, one out of two anyway :)
[00:20] <mhall119> imnichol: I haven't tried it, but the camera should be accessible using the Qt APIs
[00:20] <mhall119> http://qt-project.org/doc/qt-5.0/qtmultimedia/cameraoverview.html
[00:20] <imnichol> And a follow-up, what's the keyword that I should search for if I'm trying to find the code for picking a picture that's already been taken on the device
[00:20] <imnichol> Hah, thanks man
[00:21] <imnichol> I feel like it was "image picker" or "gallery chooser" or something like that
[00:21] <mhall119> imnichol: for pictures already taken, you want to talk to kenvandine about his content-hub
[00:21] <imnichol> "content-hub", gotcha
[00:21] <mhall119> pretty sure that was the name of it
[00:21] <imnichol> Yeah it is
[00:21] <imnichol> I remember now
[00:21] <mhall119> yeah, that'll let you get pictures even if they're outside of your app's security sandbox
[00:21] <imnichol> Thank you very much dude
[00:22] <mhall119> np, happy  hacking :)
[05:37] <mihir_> Goodmorning :)
[07:29] <vadi> I compiled my Qt app on Qt5 (installed from Qt's online installer) and there is no appmenu integration anymore. How can I get that back?
[07:45] <dholbach> good morning
[08:14] <nerochiaro> gusch: do you have time for a quick look at this ? https://code.launchpad.net/~amanzi-team/webapps-demo/webapps-demo-no-hud/+merge/184535
[08:14] <gusch> nerochiaro: ok
[08:14] <nerochiaro> gusch: thanks
[08:15] <gusch> nerochiaro: ah - that's the one, where I proposed to keep the "," for the webbrowser-app
[08:15] <nerochiaro> gusch: oh :) right, doing it now. sorry
[08:17] <nerochiaro> gusch: done
[08:18] <gusch> nerochiaro: approved - jenkins will do the rest
[08:21] <JamesTait> Good morning all, happy Swap Ideas Day! :-D
[08:22] <nerochiaro> gusch: excellent
[08:23] <nerochiaro> JamesTait: every morning i wonder, where do you find out what Weird Stuff Day is today ?
[08:25] <JamesTait> nerochiaro: wikipedia and daysoftheyear.com, mostly. Various history sites as well, but only if the first two turn up nothing that piques my interest.
[08:25] <nerochiaro> JamesTait: nice. thanks
[08:34] <mardy> timp: hi! Not sure you are the right person to review this, but at least you should know who is: https://code.launchpad.net/~mardy/ubuntu-ui-toolkit/lp1221707/+merge/184513
[08:35] <mardy> bzoltan1: or you (hi!) :-) ^
[08:57] <timp> mardy: yes I could review it.
[08:57] <timp> mardy: or zsombi
[08:57] <mardy> timp: thanks either way :-)
[08:58] <timp> mardy: ok. I'll check it later today
[09:38] <mehow> shigar and a waffle ?
[09:38] <mehow> http://www.youtube.com/watch?v=HXJefJOU5OE&noredirect=1
[09:45] <bzoltan1> hello mardy!
[09:45] <mardy> bzoltan1: hi!
[09:46] <bzoltan1> Pat told me that you might be good to join us :) and give some love to our QtCreator plugins
[09:50] <mardy> bzoltan1: that is news to me, but if I can, I'll happily help
[09:51] <bzoltan1> mardy: Well :) maybe I should have talked to David first :)
[09:52] <bzoltan1> mardy: my dear fellow jppiiroinen quits us this month and so the QtC plugins will fall on my shoulder ...
[09:54] <mardy> jppiiroinen: shame on you! ;-)
[09:55] <mardy> bzoltan1: don't tell me you are unhappy to be back to coding :-)
[09:55] <bzoltan1> mardy: To be frank :) I did enjoy when i had to code C++ the plugin when jp was out for a month
[10:09] <jppiiroinen> mardy :D
[10:11] <nik90|Office> zsombi: do you happen to know Charles Kerr's email? I can email and check if he is still working on the notifications. I forgot to mention this in our email
[10:13] <zsombi> nik90|Office I gave his email to you once already :)
[10:14] <nik90|Office> zsombi: sorry, it is in my other laptop :P
[10:16] <zsombi> nik90|Office emailed 2 U :)
[10:16] <nik90|Office> zsombi: hehe thnx a lot :). I have added him as a contact now
[10:49] <nerochiaro> gusch|lunch: i'm trying to build the gallery, but i get this error: http://pastebin.ubuntu.com/6087415/ (this is frrom trunk, on saucy)
[10:49] <nerochiaro> any ideas ?
[10:53] <gusch> nerochiaro: you need to install the content-hub
[10:54] <nerochiaro> gusch: shouldn't it be a dependency ?
[10:54] <nerochiaro> gusch: cmake doesn't complain about it being missin
[10:54] <gusch> nerochiaro: libcontent-hub-dev is set as dependency
[10:54] <nerochiaro> gusch: but cmake doesn't check for it. it should
[10:55] <gusch> nerochiaro: yes, it should, but there is no proper file for it yet in content-hub
[10:57] <nerochiaro> gusch: understood
[11:00] <nerochiaro> gusch: and when trying to run ap tests on the desktop, do you know why ap is complaining that "ImportError: No module named ubuntuuitoolkit"
[11:00] <nerochiaro> ?
[11:01] <gusch> nerochiaro: what? the gallery c++ unit test you mean?
[11:02] <nerochiaro> gusch: the galllery autopilot tests
[11:04] <gusch> nerochiaro: let me check - but they worked a few days ago
[11:08] <gusch> nerochiaro: works for me - strange message what's "ubuntuuitoolkit" supposed to be?
[11:09] <nerochiaro> gusch: i think the sdk installs some python modules to help with writing tests that do stuff like revealing the toolbar
[11:09] <nerochiaro> gusch: guess that for some reason i don't have that stuff installed here
[11:10] <gusch> nerochiaro: ah - it's a python error ...
[11:10] <nerochiaro> gusch: ok, found out what it was: ubuntu-ui-toolkit-autopilot package was missing
[11:10] <gusch> nerochiaro: you need ubuntu-ui-toolkit-autopilot
[11:10] <nerochiaro> gusch: :)
[11:21] <nerochiaro> gusch: ok, this is quite weird. i have submitted this MR and the tests pass on desktop: https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-actions-api/+merge/184533 but obviously jenkins doesn't like this stuff and lots of tests fail there. any ideas ? the tests that fail don't seem very related to the changes i made
[11:22] <gusch> nerochiaro: let me see - bzoltan had quite a lot of issues with gallery tests as well :(
[11:23] <bzoltan> gusch: yes, we have an MR pending for similar reason, timp can tell
[11:24] <gusch> nerochiaro: ^
[11:28] <nerochiaro> bzoltan: is anyone looking into these failures then ?
[11:35] <nerochiaro> timp: ^
[11:38] <mefrio> hi guys is there anybody who can help me with a click package of my app?
[11:40] <bzoltan> nerochiaro: check with the devs of those tests... that is what I try to do
[11:40] <timp> nerochiaro: no, and I have the reverse problem. Gallery tests fail for me when I run it on device
[11:41] <timp> nerochiaro gusch so I we have to fix these test issues together. I don't think someone else is looking into them.
[11:42] <cwayne> Kaleo: hey, does an app have to explictly set its background as Theme.palette.normal.background in order to have it changed when the default theme is changed?
[11:43] <nerochiaro> timp: gusch: i'm going to lunch. by the time i am back omer should be back too. hopefully he's not too busy and we can talk to him as well. i have a feeling we need a qa person to solve this mess.
[11:43] <timp> nerochiaro, gusch test reports like this https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/646/testReport/junit/gallery_app.tests.test_album_editor/TestAlbumEditor/test_add_photo_with_touch_/ are like chinese for me. I don't see what's wrong
[11:44] <timp> nerochiaro: enjoy your meal, and about the mess I really wish to get it fixed today
[11:44] <nerochiaro> timp: yeah, it fails to do something that it is expected by the test (open an album in this case). but there's no change i made that should prevent that from happening
[11:44] <nerochiaro> timp: did you try to run the tests on trunk as well ?
[11:44] <nerochiaro> timp: if not please have a go at that to see if they fail for you there too
[11:44] <timp> nerochiaro: trunk of what?
[11:44] <nerochiaro> timp: of gallery app ?
[11:45] <nerochiaro> that's what we're talking about no ?
[11:45] <timp> nerochiaro: I tried on the latest image with updated packages (apt-get update&&upgrade), and it fails, without installing custom packages
[11:45] <gusch> timp: this seems to be the issue: file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/Page.qml:155: TypeError: Cannot read property 'actionManager' of null
[11:45] <timp> nerochiaro: yes, we are. I also like to test my own UITK packages but I didn't get to it because the tests fail even with the released version.
[11:46] <nerochiaro> timp: good. let's talk with QA when i'm back then
[11:46] <gusch> dpm: can you help mefrio regarding click package issues?
[11:47] <timp> gusch: what's the url of the log where you get that?
[11:47] <gusch> timp: the one you posted
[11:47] <mefrio> dpm, if you have time please give a look at my app: https://github.com/Mefrio/Memories I want to build a click package, but I don't know how since I am using CMake
[11:48] <timp> gusch: ok, so                 var manager = page.__propagated.actionManager;
[11:48] <timp> __progagated comes from the MainView. Can the Page be instantiated before the MainView?
[11:48] <gusch> timp: and even before there is file:///usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/MainView.qml:250:39: Unable to assign Tab_QMLTYPE_33 to Page_QMLTYPE_25
[11:50] <gusch> mefrio: here a blog entry from mzanetti that might help you http://notyetthere.org/?p=316
[11:50] <timp> gusch: hmm, weird stuff happening to bindings there
[11:50] <mefrio> gusch, thank you!
[11:51] <timp> gusch: do you get those warnings also when running gallery?
[11:53] <timp> gusch: what are the dependencies on the device before I can execute ./runOnDevice.sh?
[11:54] <gusch> timp: ./runOnDevice.sh -s
[11:54] <timp> thanks
[11:54] <gusch> timp: works locally - eitehr a device issue, or a jenkins issue? (or setup on these)
[11:55] <timp> gusch: locally means on your pc? or on your phone?
[11:56] <timp> gusch: I am not aware of changes to the UITK in the code that gives the warnings here, so there is something strange
[11:56] <gusch> timp: on the desktop - didin't test on the device
[11:56] <timp> gusch: did we switch to qt5.1 yet on the device?
[11:56] <gusch> timp: ask a SDK-guy ;) - no idea
[11:57] <timp> Mirv: did we switch to qt5.1 yet on the device?
[12:00] <gusch> timp: oh - I just saw I do get those warnings on my desktop as well
[12:00] <gusch> timp: but gallery seems to work fine
[12:00] <timp> gusch: I am able to run the gallery fine on device, but autopilot tests fail
[12:02] <timp> gusch: https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-mako/646/testReport/junit/gallery_app.tests.test_album_editor/TestAlbumEditor/test_add_photo_with_touch_/ finishes with MismatchError: After 10.0 seconds test on AlbumViewerAnimated.isOpen failed: False != dbus.Boolean(True, variant_level=1)
[12:03] <timp> gusch: ok, building gallery trunk on device now
[12:06] <timp> gusch: do you have a device to run the autopilot tests on?
[12:07] <gusch> timp: starting to test it
[12:07] <timp> gusch: something like phablet-test-run -s 014E281217013001 -n -p 'gallery-app-autopilot' gallery_app should work if you have the device environment set up
[12:07] <timp> gusch: ok great :) I had a bit of a struggle to get it working, but now it works for me.
[12:07] <timp> gusch: just updating to the latest environment always takes a long time
[12:13] <timp> gusch: does runOnDevice install gallery app? so after running the script, if I open gallery-app by tapping its icon in Applications, it gives me the version that I just compiled
[12:13] <timp> ?
[12:14] <gusch> timp: no - it only local in /home/phablet/gallery afaik
[12:16] <Mirv> timp: no, need to get eg. that ui-toolkit tests problem fixed https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1217331
[12:16] <ubot2`> Launchpad bug 1217331 in Ubuntu UI Toolkit "ui-toolkit fails some tests against Qt 5.1.1" [Critical,In progress]
[12:16] <timp> gusch: so for the autopilot tests with that version I need to run phablet-test-run -s 014E281217013001 -n -p 'gallery-app-autopilot' /home/phablet/gallery/src/gallery-app ?
[12:16] <timp> Mirv: ok, just trying to figure out what has changed recently that is causing a lot of tests to fail
[12:17] <timp> so its not a new qt version
[12:17] <gusch> timp: I have to admit I don't know - haven't really worked on gallery for a while - and stuff changed quite a lot
[12:20] <timp> gusch: it doesn't run on device for me https://pastebin.canonical.com/97260/
[12:20] <timp> gusch: ok
[12:20] <gusch> timp: simply running "phablet-test-run -p gallery-app-autopilot gallery_app" on maguro with latest image works for me
[12:21] <timp> gusch: how do you install the latest image? We have several latest images
[12:22] <gusch> timp: phablet-flash cdimage-touch --pending
[12:22] <timp> gusch: that's all? no package updates?
[12:23]  * timp doing the same now
[12:24] <gusch> timp: then installing openssh-server (I don't know if that is still needed)
[12:24] <gusch> timp: and then simply "phablet-test-run -p gallery-app-autopilot gallery_app"
[12:31] <timp> gusch: could you check if webbrowser-app and notes-app autopilot tests are also succesfull for you?
[12:37] <timp> gusch, bzoltan I created two bug reports: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1223326 and https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1223329
[12:37] <ubot2`> Launchpad bug 1223326 in Ubuntu UI Toolkit "Assigning Tab to activePage when running gallery-app on device" [Critical,New]
[12:37] <ubot2`> Launchpad bug 1223329 in Ubuntu UI Toolkit "When running gallery-app on device, page doesn't have __propagated" [Critical,New]
[12:37] <timp> gusch, bzoltan they are warning that show up in the failing tests.. but I don't know if they are the cause for the fail
[12:37] <gusch> timp: notes-app works (but gallery-app did as well)
[12:38] <timp> I should be able to fix them relatively fast by adding extra guards in the uitk code
[12:38] <timp> gusch: thanks for checking.
[12:39] <timp> gusch: last time I tested, I installed the image without --pending, but I did apt-get update && apt-get upgrade before running the test
[12:39] <timp> gusch: so apparently that leaves me with a different environment than simply installing the pending image
[12:40] <timp> gusch: so when you run gallery-app on your pc, you get the warnings from my bugs also?
[12:40] <timp> gusch: I want to fix the bugs, and I can test quicker on my laptop than on device
[12:41] <gusch> timp: yes (as soon as I open the albums tab), but gallery seems to work nicely
[12:42] <timp> well it won't hurt to fix the warnings anyway
[12:45] <timp> welcome back nerochiaro
[12:45] <nerochiaro> timp: hi
[12:46] <nerochiaro> timp: i posted this fake MR to see what jenkins would do with running tests on trunk: https://code.launchpad.net/~uriboni/gallery-app/gallery-app-test-tests/+merge/184764
[12:46] <nerochiaro> timp: it has just a text file added, so if tests fail on that branch it means that jenkins is busted
[12:46] <timp> nerochiaro, gusch when I compile gallery-app on my laptop some header is missing: https://pastebin.canonical.com/97262/
[12:46] <timp> nerochiaro: ok, good to check.
[12:47] <timp> nerochiaro, gusch how so I get the build dependencies of gallery-app?
[12:47] <nerochiaro> timp: install libcontent-hub-dev,
[12:48] <gusch> timp: sudo apt-get build-dep gallery-app
[12:48] <timp> thanks
[12:48] <gusch> timp: and "sudo apt-get build-dep gallery-app-autopilot" if you want to run the autopilot tests
[12:49] <gusch> timp: no - I guess the last one does not work
[12:51] <timp> gusch: awesome. gallery-app runs now without having to comment out all the HUD code (which I needed to do long time ago)
[12:53] <timp> ah I still get the warnings
[12:53] <timp> gusch: EditingHUD is still used?
[12:53] <gusch> timp: at least a bit of progress in 3 month ;)
[12:54] <gusch> timp: yes - well nerochiaro is working on it
[12:54] <timp> I cannot open a photo - https://pastebin.canonical.com/97263/
[12:54] <timp> no animateOpen function
[12:56] <nerochiaro> timp: gusch: you can find here the version that uses actions instad of hud: https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-actions-api
[12:59] <gusch> timp: well - you don't have the HUD stuff installed (anymore?)
[12:59] <gusch> timp: the Ubuntu.HUD module
[13:00] <nerochiaro> gust, timp the hud-less version of gallery is here: https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-actions-api
[13:00] <nerochiaro> timp: i suggest you use that one instead
[13:01] <timp> nerochiaro: is that going into trunk soon?
[13:01] <timp> gusch: no I don't have that on my laptop
[13:01] <nerochiaro> timp: when jenkins stops being a pain in the arse, and the someone will have to review it. you and gusch are the best candidates
[13:01] <timp> ok
[13:01] <timp> I'll get that branch then
[13:05] <timp> nerochiaro: are there any other changes in that branch besides HUD removal?
[13:05] <timp> nerochiaro: it would be pointless for me to try the tests with that branch if they still fail on trunk
[13:06] <nik90|Office> nerochiaro: the branch  https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-actions-api requires some more fixes which I have commented on.
[13:07] <nerochiaro> timp: no, it's just hud removal
[13:09] <gusch> bzoltan timp nerochiaro this "fixes" all the issues https://code.launchpad.net/~schwann/gallery-app/gallery-disable-autopilot-tests/+merge/184773
[13:09] <bzoltan> gusch: _ALL_ ? Cool.... will it fix the water tap in my kitchen too?
[13:09] <nerochiaro> gusch: lol, that's a magic bullet indeed :)
[13:11] <gusch> bzoltan: you could fix the water tap issue in a similar way - turn off the water for the whole building ;)
[13:11] <timp> haha :)
[13:11] <bzoltan> gusch: LOL
[13:11] <timp> gusch: are you planning to get that MR approved, and then add tests back one by one?
[13:12] <nerochiaro> nik90: that's a nice tip, but it's mostly cosmetic. in all other apps i converted i have imported actions that way, i think i'll leave it that way for now, for consistency, then change it in all places later on in one go
[13:13] <gusch> timp: that MR is just a joke - my sense of humor
[13:14] <timp> nerochiaro: the change is not only cosmetic. the UITK actions allow you to set an iconSource in case you put the action in the toolbar
[13:14] <timp> gusch: I approved it already
[13:14] <timp> >;)
[13:15] <gusch> timp: it will fail without setting the commit message ...
[13:15] <timp> gusch: I don't know if it the same for all projects, but for UITK it doesn't anymore since a week or so (it takes the description when there is no commit message)
[13:16] <nerochiaro> timp: so one can import the same actions in two ways, but one is better than the other ? doesn't sound like a great design. why not just allow one kind of action ?
[13:17] <timp> nerochiaro: the way you do it was the way to do it before HUD was supported by UITK
[13:17] <nerochiaro> timp: gusch: ok, this is interesting.  jenkins likes my no-change MR, it does not fail test: https://code.launchpad.net/~uriboni/gallery-app/gallery-app-test-tests/+merge/184764
[13:17] <timp> nerochiaro: now UITK imports the Unity actions for you
[13:17] <timp> nerochiaro: trigger it again, to see if it reproducible
[13:17] <nerochiaro> timp: ah, ok. well, it's not an error to do it this way anyway, and i'd rather change all of these apps later in one go
[13:17] <nerochiaro> timp: ok
[13:18] <nerochiaro> om26er: are you a bit less busy today ?
[13:19] <nerochiaro> om26er: we're trying to figure out why https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-actions-api/+merge/184533 fails on stuff that's unrelated to the changes in the MR
[13:19] <timp> nerochiaro: ok
[13:19] <om26er> nerochiaro, that branch does not open
[13:19] <timp> nerochiaro: unfortunately the passed tests don't show any log, so I cannot see if the warnings of the failed tests are there anyway
[13:20] <timp> nerochiaro: the warnings of these bugs https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1223326 and https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1223329
[13:20] <ubot2`> Launchpad bug 1223326 in Ubuntu UI Toolkit "Assigning Tab to activePage when running gallery-app on device" [Critical,New]
[13:20] <ubot2`> Launchpad bug 1223329 in Ubuntu UI Toolkit "When running gallery-app on device, page doesn't have __propagated" [Critical,New]
[13:20] <om26er> oh ah, I am not logged in to launchpad :p
[13:21] <nerochiaro> om26er: what, this one ? https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-actions-api/+merge/184533
[13:22] <timp> nerochiaro: ok your branch runs beautifully on my laptop :)
[13:22] <timp> nerochiaro: it is just a bit annoying that I have to open the toolbar all the time to go back ;)
[13:22] <nerochiaro> timp: isn't that by design ?
[13:22] <timp> nerochiaro: I have MRs ready to improve that, but cannot get anything in until we have the autopilot tests for gallery-app passing
[13:22] <nerochiaro> timp: and what about the tests ?
[13:22] <timp> nerochiaro: tests are next to run
[13:23] <timp> nerochiaro: what's the command to run them?
[13:23] <nerochiaro> timp: cd tests/autopilot then autopilot run gallery_app
[13:23] <nerochiaro> timp: then go get a coffee
[13:25] <timp> nerochiaro: damn I don't have coffee here
[13:25] <timp> nerochiaro: can you recommend me a place? (in barcelona) :)
[13:25] <beuno>     "policy_groups": [
[13:25] <beuno>         ""
[13:25] <beuno>     ],
[13:25] <beuno> ah, no jdstrand
[13:25] <nerochiaro> timp: i don't do coffee ;)
[13:33] <rschroll> I'm trying to build a click package for a compiled app, following mzanetti's instructions.  The build seems to work, but installation (on a desktop VM) doesn't.  Is anyone available to help troubleshoot?
[13:37] <timp> nerochiaro, gusch nero's branch fails for me
[13:37] <timp> the autopilot tests
[13:37] <timp> ah no shit i ran the test for trunk
[13:39] <timp> re-running them...
[13:40] <mzanetti> rschroll: shoot
[13:41] <rschroll> My source is here: https://github.com/rschroll/beru, with the manifest and apparmor profiles
[13:41] <rschroll> there's a makeclick.sh script that copies them into a subdirectory and then calls click build
[13:42] <rschroll> That works, but if I try to install with pkcon, I get a Python traceback: dbus.exceptions.UnknownMethodException: org.freedesktop.DBus.Error.UnknownMethod: Unknown method: CreateTransaction is not a valid method of interface org.freedesktop.PackageKit
[13:42] <rschroll> This is on a VM running an up-to-date 13.10
[13:43] <rschroll> Trying to install with sudo click install gives a variety of errors; right now it's complaining that it can't generate an apparmor profile.
[13:44] <tiagoscd> hey, morning
[13:44] <tiagoscd> I would like to know if I need any specific permission to access hardware (like camera) directly via an app
[13:44] <rschroll> If I remove the read_path and write_path, that error goes away, but it says "Could not parse click manifest".  (This is on install, not build!)
[13:51] <timp> nerochiaro: ok, the tests passed on your branch for me
[13:51] <timp> nerochiaro: on laptop.
[13:51] <timp> nerochiaro: next on device
[13:52] <nerochiaro> om26er: any news ?
[13:53] <timp> 14:24 < gusch> timp: then installing openssh-server (I don't know if that is still needed)
[13:53] <timp> gusch: ^ runOnDevice.sh -s installs openssh-server :)
[13:55] <rschroll> mzanetti: I should add that first attempt to install with click install worked. But installing newer versions on top of it didn't update the apparmor profile.  I couldn't find an uninstall option, so I nuked everything in /opt/click.ubuntu.com and /var/lib/apparmor, but now I'm getting these errors.  Is there something else hanging around that could be causing problems?
[14:10] <attente> is there a way to apply the addDisplaced and removeDisplaced transitions to a ListView section.delegate?
[14:10] <attente> setting the transitions only seems to make them apply to the non-section delegates
[14:15] <om26er> nerochiaro, working on it. probably the device didn't had the latest image. Flashing now
[14:18] <timp> Wellark: is it okay to call actionManager.addLocalContext(actionContext) twice with the same actionContext?
[14:37] <seb128> timp, ^ do you know about the delegate question asked a bit earlier?
[14:38] <timp> nerochiaro: your branch seems to run fine on device. how would I run the autopilot tests for that branch on device?
[14:38] <timp> seb128: can you paste it again? I don't see it
[14:38] <seb128> timp, the one from attente 30 minutes ago
[14:38] <seb128> timp, sorry just trying to figure who could help/answer that, that's for settings work
[14:39] <nerochiaro> timp: install the package, install the gallery-app-autopilot package, shell in as phablet then when your phone is unlocked do: autopilot run gallery_app
[14:39] <nerochiaro> timp: that's exactly what i'm doing right now btw
[14:40] <attente> timp: "is there a way to apply the addDisplaced and removeDisplaced transitions to a ListView section.delegate?
[14:40] <attente> setting the transitions only seems to make them apply to the non-section delegates"
[14:40] <timp> attente, seb128 sorry, no idea
[14:41] <seb128> timp, do you know who would have one?
[14:41] <timp> attente: perhaps you can put an addition Item around your delegate that is positioned, and add sth like x:-10 to your delegate? I'm just guessing
[14:41] <timp> seb128: you can try zsombi
[14:41] <timp> seb128: he seems to be away at the moment
[14:41] <seb128> k
[14:42] <timp> nerochiaro: I executed runOnDevice.sh but that doesn't build the package
[14:43] <attente> i'm not sure ListView section.delegates have any concept of the non-section delegates they precede
[14:43] <timp> nerochiaro: I'm using cdimage-touch, no need to unlock the device. I hope that's not terribly deprecated
[14:43] <timp> ..yet
[14:43] <timp> nerochiaro: do you have a recipe for building and installing the package? or do you do it via qtcreator?
[14:44] <nerochiaro> timp: unlock as in having the lock/welcome screen up
[14:44] <timp> ah :)
[14:44] <nerochiaro> timp: i downloaded the package from jenkins
[14:45] <nerochiaro> timp: you can also build in pbuild
[14:45] <nerochiaro> timp: om26er: all tests passed on my device using the package downloaded from the latest run of jenkins on this: https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-actions-api/+merge/184533
[14:45] <nerochiaro> timp: om26er: but jenkins fails on the same packages
[14:46] <nerochiaro> om26er: latest image, just flashed
[14:50] <mefrio> mzanetti, ping
[14:51] <mzanetti> mefrio: pong
[14:52] <mefrio> mzanetti, I was reading your blog entry to learn how to build a click package for my app (http://notyetthere.org/?p=316) but I have a question....in the first point you said that the developer should build an arm package using pbuilder environment
[14:52] <mefrio> mzanetti, could you explain me how to do that? I did not find anything useful
[14:54] <mzanetti> mefrio: do you have debian packaging files (for creating a .deb) package?
[14:54] <mefrio> mzanetti, yes
[14:54] <mzanetti> mefrio: check the comments, there is a command to setup pbuilder
[14:54] <mzanetti> mefrio: but isntead of manually unpacking the created chroot
[14:55] <mzanetti> mefrio: do a "pbuilder -p saucy-armhf"
[14:56] <mefrio> mzanetti, let me see
[14:56] <timp> nerochiaro: which package has unzip?
[14:57] <nerochiaro> timp: unzip  ?
[14:57] <mzanetti> timp: apt-cache search has it :D
[14:59] <timp> yes, it is there. for some reason I didn't see it repeatedly
[14:59] <timp> :s
[15:02] <timp> nerochiaro: the tests fail instantly https://pastebin.canonical.com/97273/
[15:02] <timp> nerochiaro: are you sure you run it as phablet? the permissions seem wrong
[15:02] <timp> hmm
[15:03] <timp> ah I ran it as root first
[15:03] <nerochiaro> timp: :)
[15:04] <timp> nerochiaro: ok, something seems to be happening now, but I don't see gallery opening on the device
[15:04] <nerochiaro> timp: and you're sure the welcome screen was gone when you laucnhed that command ?
[15:04] <timp> DBusException: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
[15:05] <timp> nerochiaro: yes it was gone
[15:05] <nerochiaro> timp: i am now afraid you messed something up by runing things as root
[15:07] <timp> hmm
[15:08] <timp> nerochiaro: su - phablet instead of su phablet works :)
[15:08]  * timp running tests now
[15:08] <timp> I log in using adb which gives me a root shell
[15:11] <timp> nerochiaro: I have an MR to fix some warnings in the gallery-app tests: https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/gallery-app-warnings/+merge/184788
[15:11] <timp> nerochiaro: could you test them on device with your gallery-app branch? uitk packages are in the MR
[15:12] <timp> I can test them also, but I'm still testing your branch with stock UITK on device
[15:12] <nerochiaro> timp: ok, doing it
[15:12] <timp> thanks
[15:12] <timp> I am not sure if the warnings are related to the fails
[15:12] <timp> nerochiaro: please post the results as comments on the MR
[15:14] <nerochiaro> timp: btw my branch with stock uitk pass all tests
[15:14] <nerochiaro> timp: on device
[15:17] <timp> nerochiaro: I just got the same results. good.
[15:17] <timp> so what's up with jenkins?
[15:21] <timp> nerochiaro: I am now re-running the test with my UITK version
[15:21] <timp> nerochiaro: we should test jenkins for your MR with my UITK version, dunno if that's possible.
[15:21] <nerochiaro> timp: i don't think it's possible
[15:22] <nerochiaro> timp: but in any case just my MR failing alone in jenkins and working on the device is something that om26er needs to help us fix. as far as i'm concerned all the tests are good, i can't find out what's broken
[15:23] <nerochiaro> timp: and for the record, tests just finished here, with my branch + your uitk branch > everything pass
[15:23] <nerochiaro> timp: so there's something busted in jenkins
[15:23] <nerochiaro> om26er: let me know if you want me to file a bug for this
[15:23] <om26er> nerochiaro, I have flashed the device
[15:23] <om26er> nerochiaro, but somehow I lost the MR you gave me
[15:24] <timp> om26er: https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-actions-api/+merge/184533
[15:24] <timp> om26er: I verified that the autopilot tests pass with the latest pending image
[15:24] <nerochiaro> om26er: also your fix on the mediaplayer MR isn't working: https://code.launchpad.net/~amanzi-team/mediaplayer-app/mediaplayer-app-new-actions-api/+merge/182148
[15:24] <timp> omg26er: so cdimage-touch --pending. Is that what jenkins uses?
[15:25] <timp> nerochiaro, om26er the results say UNSTABLE, not FAILED. What's the difference?
[15:25] <om26er> timp, yes we do --pending
[15:25] <om26er> timp, unstable means few tests failed. FAILED means all
[15:26] <om26er> timp, nerochiaro its rerunning here
[15:26] <om26er> s-jenkins:8080/job/generic-mediumtests-runner-maguro/657/console
[15:27] <om26er> only on one device, I just wanted to make sure
[15:27] <timp> a bunch of tests failed, but I don't see a relation between the failed tests
[15:29]  * timp food now. bbl.
[15:29] <mefrio> mzanetti, I tried to follow the instructions in a comment but it seems pbuilder cannot create a valid arm environment
[15:30] <mefrio> mzanetti, it seems the .tgz created is empty
[15:31] <om26er> timp, nerochiaro that passed. So we should re-run the CI and it will pass this time
[15:32] <nerochiaro> om26er: why would it pass ?
[15:32] <nerochiaro> om26er: it didn't pass before and there are no changes in the branch
[15:32] <mzanetti> mefrio: paste the whole output
[15:32] <om26er> nerochiaro, the device flashing was kind of stuck a 2 days behind
[15:32] <om26er> so I flashed to the latest iamge
[15:33] <om26er> nerochiaro, about the mediaplayer failure you just pointed at that's a different thing. a problem with jenkins. We need to retrigger again
[15:33] <om26er> https://jenkins.qa.ubuntu.com/job/generic-mediumtests-runner-saucy/2738/console
[15:33] <om26er> see the logs
[15:33] <nerochiaro> om26er: ok, will retryigger both
[15:33] <mefrio> mzanetti, http://pastebin.com/uw5gdYXX
[15:33] <om26er> nerochiaro, I did that already
[15:33] <nerochiaro> om26er: on both ? ok
[15:34] <mzanetti> mefrio: download error...
[15:35] <mzanetti> mefrio: make sure your network is working
[15:35] <mzanetti> mefrio: and make sure your system is up to date
[15:35] <mefrio> oh I did not noticed that error...mzanetti thanks
[15:35] <mefrio> let me retry
[15:35] <om26er> yep
[15:38] <Wellark> timp: yes. each of the add* functions are safe to call multiple times with same data
[15:53] <labsin> which path do I need to give to the icon in my desktop file for a click package. Is it "./some-name.png" or just "some-name.png" cause the first one was working on my desktop before but not anymore.
[15:56] <iBelieve> labsin, "some-name.png" is correct
[16:07] <mefrio> mzanetti, it worked! Thanks! :)
[16:07] <mzanetti> :)
[16:13] <mefrio> mzanetti, the chroot environment cannot found my home dir :(
[16:14] <mzanetti> mefrio: you can do "ptest --save -p saucy-armhf"
[16:15] <mzanetti> mefrio: inside you can create the required dirs and then type "logout" to exit the chroot again
[16:15] <mzanetti> mefrio: any changes in there will only be saved when you give the --save option
[16:15] <mefrio> mzanetti, ok thanks now it works
[16:43] <AskUbuntu> Where do I submit applications written for Ubuntu Touch? | http://askubuntu.com/q/343877
[16:48] <balloons> iBelieve, another day of test results :-) Did you happen to take a look?
[16:50] <iBelieve> balloons, no, I haven't seen test results. Where? Are the tests still failing?
[16:52] <balloons> iBelieve, yea, I'm not sure why.. I'll be back a bit later, but have a look if you'd like
[16:52] <balloons> iBelieve, the results appear everyday here: http://reports.qa.ubuntu.com/smokeng/
[16:53] <balloons> iBelieve, I didn't see evidence of a systematic failure occuring; meaning, different tests simply failed there asserts at different points, indicative of actual test failures
[16:54] <balloons> the good news is the Xauthority problem is solved :-)
[16:54] <nerochiaro> om26er: gallery still failing https://code.launchpad.net/~amanzi-team/gallery-app/gallery-app-actions-api/+merge/184533
[16:55] <om26er> nerochiaro, we just updated java on the slave
[16:55] <iBelieve> balloons, that's weird, it looks like it doesn't think None == None
[16:56] <om26er> nerochiaro, sorry about keeping your builds failed. I triggered a rebuild (now that we have a latest Java)
[16:56] <nerochiaro> om26er: ok. can you retrigger the other one too ? https://code.launchpad.net/~amanzi-team/mediaplayer-app/mediaplayer-app-new-actions-api/+merge/182148
[16:56] <om26er> nerochiaro, ok
[17:03] <clepto> mhall119, any news on compiled binaries in click packages?
[17:04] <mhall119> clepto: I'm still finding out myself, dpm and dholbach should know more
[17:04] <dholbach> we're going to have a tutorial up soon which will sort of be a workaround
[17:04] <clepto> mhall119, dholbach thank you both!
[17:04] <dholbach> but everybody's hard at work getting things ready, so we can have stuff build automatically in the future
[17:04] <dholbach> rock on!
[17:07] <iBelieve> I'm filling out the Submission Form for the App Showdown. What do I put in the Submission URL field?
[17:08] <clepto> iBelieve, submission form?
[17:08] <iBelieve> clepto, https://docs.google.com/forms/d/1a1Owwl6EVQ8165Wy_TsSaDGGWmYJaT6INm2P4DgZWAA/viewform
[17:09] <iBelieve> clepto, Item #4 of http://developer.ubuntu.com/showdown/
[17:12] <iBelieve> mhall119, do you know what I should put for the Submission URL of the submission form for the showdown? ^^^
[17:12] <dpm> iBelieve, that will be the url of your app in myapps.developer.ubuntu.com, let me give you an example...
[17:12] <iBelieve> dpm, so https://myapps.developer.ubuntu.com/dev/click-apps/13/?
[17:12] <dpm> iBelieve, exactly :)
[17:13] <iBelieve> dpm, great, thanks. Should I fill in the form now or is there any reason to wait?
[17:13] <dpm> iBelieve, go for it, no reason to wait :)
[17:13] <iBelieve> dpm, cool, thanks
[17:16] <iBelieve> dpm, for the website, should I put my GitHub project, my blog, or my static webpage http://sonrisesoftware.wordpress.com/ubuntu-tasks/?
[17:17] <dpm> iBelieve, any website you think offers info about the project should do. I guess you have links to github on your static webpage, so that might be a nice URL to use
[17:18] <iBelieve> dpm, okay, I'll use the static webpage
[17:18] <dpm> great
[17:19] <dpm> clepto, as dholbach is saying, we're working to get some more detailed documentation online soon. In the meantime, you can use http://developer.ubuntu.com/resources/tutorials/getting-started/creating-click-packages-with-cpp-extensions/ - although the part about doing the actual cross-compiling will need to be fleshed out
[17:21] <clepto> dpm, today I'll try to fix as many bugs as I can and focus tomorrow on packaging (8:20 pm here), do you think it will be updated by tomorrow?
[17:22] <dpm> clepto, we will do our best, but if you are on IRC tomorrow, you can ping us if we can help with any questions.
[17:22] <dpm> clepto, you'll essentially need to do two things:
[17:22] <dpm> 1) Cross-compile your extension
[17:23] <dpm> 2) Put the compiled binary in a click package that you will create manually outside of Qt Creator
[17:24] <dpm> There are ways to do 1), but we want to describe the easiest way for app developers for the contest, as a temporary solution until we've got all of the infrastructure bits sorted
[17:25] <clepto> dpm, that will be great! ok!
[17:29] <nerochiaro> renato_: can you please finally approve https://code.launchpad.net/~amanzi-team/mediaplayer-app/mediaplayer-app-new-actions-api/+merge/182148 ? now jenkins finally likes it !
[17:40] <om26er> nerochiaro, renato_ I top approved
[17:40] <nerochiaro> om26er: thanks
[17:44] <nerochiaro> om26er: the gallery app is not failing on my maguro device when using the same packages built by jenkins
[17:45] <om26er> nerochiaro, the logs suggest the app crashed
[17:45] <om26er> like real crash
[17:46] <nerochiaro> om26er: that sounds strange. and also many other tests in gallery open a photo, so i don't see why only that one should crash
[17:47] <om26er> nerochiaro, race or something probably, definitely nothing wrong with that code, rather something bad in the app that needs fixinfg
[17:50] <e8hffff> Question: What the status of the File-Manager opening files?
[17:55] <balloons> iBelieve, yes it can read a bit funny.. it's showing you the line output, none=none, but the assert is eventually(notequals(none))), hence the failure
[17:58] <mefrio> mzanetti, I am still getting errors after an afternoon spent on that click package generation...can you help me please? http://pastebin.com/T1DABeet
[17:59] <mefrio> I installed all the dependencies...it's so frustrating
[17:59] <iBelieve> balloons, oh, now i see the actual assertion. That makes a bit more sense now :)
[18:01] <balloons> iBelieve, :-) I'm going to run the whole test suite again here locally on my device.. I know I ran it yesterday and worked, so I'm confused that it is failing.
[18:03] <attente> when emitting dataChanged() in QAbstractItemModel, are there conditions where data() is not called as a result? i would've expected it to get called every time, but it seems to be not the case
[18:03] <mzanetti> mefrio: oh :/ you're running into the qemu bug
[18:03] <mzanetti> mefrio: you would need to disable the tests to build it in pbuilder
[18:03] <mefrio> mzanetti, do you need the autopilot package?
[18:04] <mzanetti> no... qmltests are causing this issue with pbuilder
[18:04] <mefrio> mzanetti, how do I disable it?
[18:04] <mzanetti> mefrio: you said you are using cmake, right?
[18:05] <mefrio> mzanetti, yes
[18:05] <mzanetti> mefrio: comment the add_subdirectory(tests)
[18:05] <mzanetti> or similar
[18:05] <mefrio> mzanetti, I have not yet implemented real tests so there is nothing releated to tests in my CMake
[18:05] <mefrio> mzanetti, do I have to disable the autopilot package so?
[18:06] <mzanetti> no... autopilot should be fine
[18:06] <mzanetti> mefrio: but according to the logs it uns this: qmltestrunner -input tests/unit
[18:06] <mzanetti> mefrio: there must be a add_test() somewhere
[18:09] <mefrio> mzanetti, can you take a look if you have time please? https://github.com/Mefrio/Memories
[18:09] <mefrio> there is nothing related to qmltestrunner in my CMake
[18:12] <mefrio> mzanetti, oh it was in the Makefile generated by QtCreator -.-
[18:12] <mzanetti> ok :)
[18:13] <mefrio> mzanetti, it's hardest to build an arm package then write an app :P can't we let launchpad do it for us?
[18:13] <mzanetti> mefrio: yes, you could. you'd need to contact the launchpad admins and ask for an arm builder for your ppa
[18:14] <mzanetti> mefrio: however, those launchpad builders have the same problem and would crash in the same way
[18:14] <mefrio> mzanetti, the arm builder should available by default, no?
[18:15] <mzanetti> mefrio: probably they will be enabled by default at some point, yes
[18:16] <mefrio> mzanetti, anyway the package it was build has the _all extension...how do I make sure it is for ARM?
[18:16] <mzanetti> the .deb package or the .click package?
[18:16] <mefrio> mzanetti, the deb
[18:16] <mzanetti> debian/control  -> Architecture
[18:17] <mefrio> mzanetti, "Architecture: all"
[18:17] <mzanetti> mefrio: you should also add your build depends in there instead of modifying your pbuilder tarball
[18:19] <mefrio> mzanetti, they are there, I thought I had to install them in the pbuilder too....anyway, is the architecture good?
[18:19] <mzanetti> mefrio: no, it should be "any"
[18:21] <mefrio> mzanetti, ok thanks for your big patience :) it seems I am finally done with that thing! :D
[18:23] <mzanetti> :)
[18:24] <mefrio> mzanetti, and of course, changing the architecture to any I get the following error http://pastebin.com/Yv5BYYgp
[18:25] <mzanetti> seems a bit like you have a dirty source directory
[18:26] <mzanetti> could it be that you tried building with debuild first and still have some x86 binaries in debian/memories-app... ?
[18:26] <mefrio> mzanetti, I deleted them
[18:27] <mefrio> let me do it again, deleting also the source build dir
[18:28] <mefrio> it's the same
[18:28] <mzanetti> lol... the app supports "basic memory management (add, remove and edit)"
[18:28] <mzanetti> oh boy... I whish I could remove memories just like that
[18:29] <mefrio> mzanetti, ahaha my app has super-natural powers xD
[18:29] <mzanetti> mefrio: does it already support all that stuff or is that the roadmap?
[18:29] <mefrio> mzanetti, it supports everything written on GitHub
[18:29] <mzanetti> not bad... time to get that stuff packaged up them
[18:30] <mefrio> mzanetti, and some more functions such PDF export for which I need a C++ module...this feature is causing me all this problems with packaging
[18:30] <mzanetti> hmm... maybe you'd be better off with just doing it manually in the chroot
[18:31] <mzanetti> as you said you have the package already I assumed it to be completely working already
[18:31] <mzanetti> so basically what you can do is to ptest into the chroot, copy the source in there, do a manual cmake and make and just copy that one .so file back to your other system and package it up
[18:31] <mzanetti> mefrio: ^
[18:32] <mefrio> mzanetti, yeah that sounds as a great solution
[18:35] <mefrio> mzanetti, with CMake and make to build it says "Error: SEGV" :'(
[18:36] <mefrio> running make again solves the segmentaion error -.-
[18:36] <mefrio> now I finally have the .so!!!!!!!!! :D yesss! :D
[18:36] <mefrio> thank you very much mzanetti!! I couldn't have done that without your help
[18:38] <mefrio> now it's time to make some rest from all that things :D see you guys and thank you again mzanetti!
[18:45] <balloons> iBelieve, the same tests failed on my device, as failed in the lab, heh
[18:45] <balloons> I wonder what has changed?
[18:55] <iBelieve> balloons, that's odd. Did you run the tests on the desktop as well? I'll run them myself in a few minutes
[19:04] <balloons> iBelieve, I had thought I had done both.. but it fails on the device now
[19:04] <balloons> it of course passed in the vm
[19:18] <boiko> bfiller: at last renato_ managed to fix the address-book-service code that was blocking the UI, no more UI freezes when the smart dialer is looking up for contacts
[19:19] <bfiller> boiko: cool, can you point me at the MR's so I can test?
[19:19] <boiko> bfiller: https://code.launchpad.net/~renatofilho/address-book-service/eventloop-wait/+merge/184842
[19:19] <boiko> bfiller: now I'll check the designs for the dialer-app
[19:34] <vadi> I compiled my Qt app on Qt5 (installed from Qt's online installer) and there is no appmenu integration anymore. How can I get that back?
[19:37] <mzanetti> vadi: afaik Qt 5 doesn't officially support that yet. Try installing the ubuntu qt5 packages
[19:38] <bfiller> boiko, renato_ : that MR looks kind of scary regarding event loops and waits and such.  Did you guys thoroughly test and make sure no regressions?
[19:38] <vadi> Are those officially available in 12.04? I used the Ubuntu Touch SDK ppa before - and it was building me a fairly broken Qt5 app (couldn't click anywhere and such). I'll try once again, though
[19:39] <mzanetti> bfiller: heh... isn't the task of the reviewer? :D
[19:40] <bfiller> mzanetti: indeed, that's why I'm asking to double check
[19:40] <boiko> bfiller: I tried the dialer-app, and the contacts app
[19:41] <renato_> bfiller, I tested both too
[19:41] <bfiller> renato_: does that code only get invoked when using the smart dialer or all the time when fetching contacts?
[19:42] <mzanetti> bfiller: just reading the code it looks ok... the one bad would assert
[19:42] <mzanetti> actually... do we test with debug builds on the phone?
[19:42] <mzanetti> otherwise I wouldn't trust that this assert gets actually discovered when it happens
[19:42] <boiko> bfiller: all the time
[22:50] <timp> Wellark: ok, great. then this MR is good :) https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/gallery-app-warnings/+merge/184788


 New External CD/DVD player starts up then goes to sleep. How do I keep it awake?
[03:57] <qwebirc6480> Evening.
[03:57] <qwebirc6480> I've found that I am literally unable to copy and paste text.
[03:57] <qwebirc6480> All because Klipper literally is *constantly* copying nothing.
[04:25] <valorie> qwebirc6480: I had the same problem until I long-pressed klipper and changed the config
[04:34] <valorie> qwebirc6480: https://imgur.com/a/xAoFpI6
[04:34] <valorie> is mine
[04:40] <qwebirc6480> no config setting helps
[06:37] <lordievader> Good morning
[10:28] <BluesKaj> hiyas all
[15:34] <reaga> how do i copy + paste a directory in kubuntu?
[15:34] <reaga> i try right click copy then right click paste in another place, nothing happens
[15:36] <diogenes_> reaga, what do you mean by nothing happens?
[15:36] <reaga> the same thing happens as if i didnt click paste
[15:36] <reaga> nothing happens
[15:37] <tyler> hi
[15:38] <tyler> i can not set up my desktop shortcut for double commander with root privileges on kubuntu 18.04
[15:38] <tyler> i was editing the exec= line with sudo but nothing happening
[15:38] <diogenes_> it doesn't show the progress bar until you click on the panel but it shoult copy the file.
[15:40] <diogenes_> tyler, what is the original Exec = command?
[15:41] <tyler> doublecmd %F
[15:41] <tyler> but works without %F also
[15:42] <diogenes_> try in terminal: pkexec doublecmd
[15:42] <tyler> ok
[15:44] <tyler> does not work
[15:45] <tyler> (doublecmd:11002): Gtk-WARNING **: 17:43:29.482: cannot open display:
[15:45] <diogenes_> sudo doublecmd works?
[15:45] <tyler> on terminal i can run the program with sudo doublecmd
[15:46] <tyler> yes that is works
[15:46] <tyler> but on the desktop shortcut just does not work
[15:46] <diogenes_> because you probably need the string: Terminal=true
[15:47] <tyler> yes that is false
[15:48] <tyler> i am trying with true value
[15:49] <tyler> yes that is fine but poping up the terminal and asking for password
[15:50] <diogenes_> because that;s how sudo works, in terminal, if you don't want a terminal to pop up then you need to install something like kdesu and run the app with: kdesu appname
[15:50] <tyler> how can i edit the .txt not asking password all the time i try to launch doublecmd?
[15:50] <diogenes_> but i'm not sure if kdesu is still maintained and available.
[15:51] <tyler> need to install kdesu from terminal then?
[15:51] <diogenes_> yeah try: sudo apt install kdesu
[15:51] <tyler> ok
[15:52] <tyler> this package can not found...
[15:52] <diogenes_> that's what i thought, they got rid of it.
[15:53] <diogenes_> is it 18.04?
[15:53] <tyler> yep
[15:53] <tyler> 18.04.2 LTS
[15:54] <tyler> KDE Plasma version 5.12.4
[15:55] <diogenes_> try: sudo apt install kdesudo
[15:56] <tyler> same: this package can not found
[15:58] <diogenes_> sudo apt install kde-cli-tools
[15:59] <tyler> yes i have got installed this already
[16:00] <diogenes_> tyler, the run this: ls /usr/bin | grep kde
[16:00] <diogenes_> copy the output and pastebin
[16:00] <diogenes_> !pastebin
[16:03] <Guest42059> abcd
[16:04] <tyler> tyler@tylerlinux:~$ ls /usr/bin | grep kde
[16:04] <tyler> dh_movelibkdeinit
[16:04] <tyler> fixkdeincludes
[16:04] <tyler> kde4
[16:04] <tyler> kde4-config
[16:04] <tyler> kde4-menu
[16:04] <tyler> kde-add-printer
[16:04] <Guest42059> leave
[16:04] <diogenes_> tyler, don't paste here directly
[16:04] <diogenes_> !pastebin | tyler
[16:04] <diogenes_> read carefully ^^^
[16:07] <tyler> https://paste.ubuntu.com/p/SWnZhZtRnV/
[16:07] <tyler> like this?
[16:08] <diogenes_> yes good job.
[16:09] <diogenes_> so your options are: 1) either tweak the sudoers file which is the risky part or 2) work with policykit
[16:10] <diogenes_> here is a good article about both those options: http://www.admin-magazine.com/Articles/Assigning-Privileges-with-sudo-and-PolicyKit
[16:10] <tyler> why is risky sudoers tweaking?
[16:11] <diogenes_> because if you put even a wrong dot in a wrong place, you break your sudo and you can no longer use sudo.
[16:13] <tyler> i see
[16:13] <tyler> lets do policykit then
[16:14] <tomreyn> visudo helps there
[16:17] <tyler> https://paste.ubuntu.com/p/XQ7Sp5pgF6/
[16:19] <tyler> in my case how need to edit it?
[16:20] <diogenes_> title is wrong, it shows: Entry] and it should be [Desktop Entry] but in any case it's not recommended to use: sudo with texteditors.
[16:25] <tyler> https://paste.ubuntu.com/p/49fFkKR5bq/
[16:26] <tyler> sorry my fault. wrong paste
[16:29] <tyler> i am looking this policykit. but can not install from terminal
[16:31] <tyler> regarding Muon i have installed this policykit-1-doc
[16:50] <tyler> no luck :(
[16:51] <tyler> still requires passw
[18:04] <obizelko> Hi all! I believe my PC is compromised. I have a log from rkhunter. Can anybody help me here?
[19:16] <tomreyn> obizelko: you could start by posting the rkhunter report to a pastbein and linking it here. most of the time, people saying what you're saying really ran into false positives, though.
[19:33] <Guest95870> ./server chat.freenode.net
[19:34] <obizelko> tomreyn: https://privatebin.net/?fde95a098febfe06#A7ZyMlFz0GmYyyYTN8sb5IjvE/oU5jLPtO7NTS/xsI4=
[19:34] <obizelko> I'm pretty sure it's not false positives.
[19:38] <OerHeks> i see no suspicious items, just 'warning' is not an intrusion, AFAIK
[19:50] <obizelko> tomreyn, OerHeks: Alright. What happened is, that my updater suddenly popped up, telling me it was unable to update. Even though I didn't try to update. It said, that it couldn't update. So, I just pressed continue. Then it wanted me to use a password, but it wasn't the traditional updater file, it was running. I tried to open the updater again, and it could update normally. That was just very suspicious. So I used rkhunter.
[19:53] <OerHeks> "it couldn't update" without the exact message, hard to tell ..
[19:53] <OerHeks> it could be valid, not able to update while an other process is using the update mechanism..
[19:53] <OerHeks> unattended updates happen to give that issue
[19:54] <OerHeks> :-)
[19:55] <obizelko> "Failur to download extra files"
[19:56] <obizelko> With a button that says: Run this action now
[19:57] <OerHeks> hmm, True Type Fonts installer?
[19:59] <obizelko> It tells me, that the following packages were requested after package installation, but the data could not be downloaded or processed
[19:59] <obizelko> I didn't try to update
[20:02] <obizelko> And when pressed the "Run this action now"-button, it wanted my password, while updating from another interface than normal
[20:54] <kerem> hello
[21:29] <Test0r> hihu, where can i download an old iso from kubuntu 14.04?
[21:42] <OerHeks> Test0r, i think you need to find the official torrent address,..
[21:46] <OerHeks> http://www.pcds.fi/downloads/operatingsystem/ubuntubased/UBUNTU/archive/kubuntu/1404LTS/rel14045/
[21:46] <OerHeks> 14.04.5
[21:46] <OerHeks> good luck, no updates
[21:46] <tyler> hi
[21:47] <tyler> wich one is correct?     root    ALL=NOPASSWD:(ALL:ALL)NOPASSWD: ALL or root ALL=(ALL:ALL)NOPASSWD: ALL  ??
[21:49] <OerHeks> terrible idea, tyler ..just saying
[21:50] <tyler> i want root privileges at aLL time for EVERYBODY for EVERYTHING. i mean running commands modify system files etc.
[21:50] <OerHeks> is this your homework?
[21:50] <tyler> i know is terrible but need to do for practice
[21:50] <OerHeks> https://help.ubuntu.com/community/RootSudo
 ALL=NOPASSWD: ALL
[21:51] <Test0r> OerHeks: thx, but no seeder :(
[21:52] <OerHeks> Test0r, oh, that was your chance.. i have no clue of a ftp with 14.04 / .5
[21:53] <Test0r> http://old-releases.ubuntu.com/releases/kubuntu/ but why no 14.04 :(
[22:03] <tyler> great
[22:03] <tyler> it works well
[22:04] <tyler> i was writing at the very end of the file root ALL=NOPASSWD: ALL


[12:17] <mdke> I'll sort it out
[12:17] <nixternal> thanks
[12:18] <somerville32> Would Xubuntu docs have the bug?
[12:19] <mdke> I'll look there too
[12:25] <mdke> done
[12:26] <mdke> nixternal: looks like edubuntu aren't using any, so we'll leave that
[12:32] <nixternal> thank you
[02:50] <theCore> mdke: ping
[02:50] <mdke> theCore: Please provide a bit of information about what you want and I will respond when I am around.
[02:50] <theCore> uh, an auto-responder?
[02:51] <theCore> nevermind, then
[02:51] <crimsun> you gave him a contentless ping
[02:52] <crimsun> in other words, don't do foo: ping
[02:52] <crimsun> do foo: ping, I need info on blah blah blah
[02:53] <crimsun> it's fairly annoying to come back, read backscroll, and find you were pinged but have no idea about what the ping was
[02:54] <LaserJock> is that what tollef's planet post was for?
[02:55] <LaserJock> I couldn't tell what you were supposed to do with it
[02:55] <crimsun> yes
[02:56] <crimsun> he recently updated/fixed his irssi script (thanks to mdke, who found some bugs)
[03:00] <mpt> Still needs wording work, apparently
[03:30] <somerville32> mdke: ping, can your script detect if my ping is not-contentless?
[03:30] <somerville32> magic
[03:34] <LaserJock> well, I assume it just looks for a line with just "ping"
[03:53] <somerville32> Maybe I'll just start ponging people instead of pinging them
[07:39] <somerville32> mdke: Can you approve my membership? Thanks :]
[09:13] <mdke> mpt: I'll accept rewording suggestions
[09:13] <mdke> somerville32: ok.
[09:13] <somerville32> mdke: thanks
[09:23] <mpt> mdke, "(I'm not here right now, but ____ )" probably would work
[09:23] <mpt> Rhe brackets being roughly equivalent to that whirring noise that alerts you to the fact that you've reached an answering machine
[09:23] <mdke> mpt: I thought of that, but what if I am here?
[09:23] <mpt> The brackets, rather
[09:24] <mpt> oh
[09:24] <mdke> ok, I've thought of something
[09:24] <mdke> brackets sounds good
[09:25] <mpt> just the brackets by themselves might be enough
[09:25] <mpt> mdke, ping?
[09:25] <mdke> mpt: (In case I'm not around at the moment, please provide a bit of information about what you want and I will respond when I get back.)
[09:25] <mdke> why thanks
[09:26] <mdke> mpt: how's it going otherwise?
[09:26] <mpt> Launchpad's test suite is hideously slow
[09:26] <mpt> Apart from that, it's well
[09:27] <mdke> good
[11:21] <mpt> svn: Failed to add file 'ubuntu/C/newtoubuntu/windows-glossary.xml': object of the same name already exists
[11:30] <bhuvan> mpt: does it happen when you do 'svn update'?
[11:31] <mpt> yes
[11:31] <mpt> I fixed it by removing the file manually, but I shouldn't have to
[11:33] <mpt> (though if I'd been merging into my own bzr branch instead of sending mdke a diff I wouldn't have had that problem in the first place)
[11:33] <mpt> Ow, yelp doesn't open pages any more
[11:34] <mpt> Entity 'rsquo' not defined
[11:35] <bhuvan> ok
[11:35] <mpt> that's strange
[11:35] <mpt> There seems to be an error in line 13 of gnome-menus-C.ent
[11:36] <mpt> oh, missing ">" character
[11:36] <mpt> Anyone want to commit that? :-)
[11:38] <mpt> This missing ">" character is at the end of line 12
[11:39] <bhuvan> i'll do
[11:40] <mpt> ta
[11:43] <bhuvan> mpt: fixed in r3630
[02:22] <jenda> mdke: ping
[02:22] <mdke> jenda: (In case I'm not around at the moment, please provide a bit of information about what you want and I will respond when I get back)
[02:22] <jenda> heh
[02:23] <jenda> mdke: who is in charge of the trademark policy page? Or, who are the people who have access? I reported this bug a month ago, and gave it a fair amount of time, because the page looks just terrible, and no one even touched it.
[02:23] <jenda> https://bugs.launchpad.net/ubuntu-website/+bug/74247
[02:23] <Ubugtu> Malone bug 74247 in ubuntu-website "http://www.ubuntu.com/ubuntu/TrademarkPolicy errata" [Undecided,Unconfirmed]
[07:42] <mdke> jenda: the problem is that not many people get bugmail about ubuntu-website. However, me assigning it to myself means that I'm going to do it
[07:48] <jenda> mdke: ah, great newz. Thanks :)
[08:51] <mdke> mpt: nice patch, thanks.
[08:52] <mdke> mpt: we can remove the "What's New Since Ubuntu 6.06 (Dapper)" as upgrades dapper->feisty won't be a supported upgrade path I think (did we already discuss this?)
[09:00] <mpt> mdke, ok
[09:01] <mdke> mpt: now we just need to figure out what to do with the Gnome stuff and the stuff about users/sudo
[09:01] <mdke> dunno if you have any thoughts on that already
[09:10] <mpt> mdke, actually, I'd forgotten the previous train of thought I had about "What's new since Ubuntu 6.06"
[09:10] <mpt> which went something like this
[09:11] <mpt> "Upgrades from 6.06 to the next LTS will be supported, but not 6.06 to 7.04, so it's not really relevant"
[09:12] <mpt> "yeah, but someone might do the supported upgrades from 6.06 -> 6.10 -> 7.04, and they won't spend enough time on 6.10 for 'What's new since 6.10' to be useful"
[09:12] <mpt> "Perhaps, but not enough people will do that for writing help for them to be useful"
[09:13] <mpt> "Oh, but, but, what about when the next LTS comes along and we *do* need that help? Wouldn't it be easier to compile it gradually, starting with the 6.10->7.04 changes, and building up from that?"
[09:20] <mpt> mdke, as for your other question, I think "Desktop Overview" will almost always be too distribution-specific for upstream to say anything useful about it
[09:21] <mpt> For example, it should begin with a screenshot overlaid with a bunch of numbered circles, and it will be pretty obvious if that screenshot isn't an Ubuntu one
[09:23] <mpt> "Desktop sessions" is written from the implementation looking up, rather than the user looking down, and probably needs a complete rewrite :-(
[09:25] <mpt> "Basic skills" makes sense, but needs much shortening
[09:35] <mdke> mpt: it might be relevant to the live cd.
[09:35] <mdke> but still.
[09:36] <nixternal> oi!
[09:36] <mdke> I wonder if those upstream things could be put into "Customising and Configuring your Desktop", as a top level topic, except basic skills, which could be in "New to Ubuntu 7.04"
[09:36] <LaserJock> umm, silly question, where is all this TBH stuff in the repo?
[09:37] <mdke> LaserJock: ubuntu/C or kubuntu/C plus generic/server
[09:37] <LaserJock> oh wow, things have changed :-)
[09:39] <mpt> mdke, yeah, quite a bit of the help should be different depending on whether you're running Ubuntu from the CD
[09:39] <theCore> I am (trying) to design the new format for Project Mallard, so I would like your opinion how tags should be used. For example, which of those three ways to label a menu would you like better? http://paste.ubuntu-nl.org/870/
[09:40] <nixternal> theCore: 3rd way
[09:40] <mpt> theCore, I don't think the format needs to distinguish between control types
[09:40] <mpt> just use  for all of them
[09:40] <nixternal> actually the 3d way needs a little tweaking
[09:40] <mdke> mpt: you need a way to get the arrows
[09:41] <mpt> and then have some element which works the way <menuchoice> does now, to put around them, that inserts arrows between them
[09:41] <theCore> well, &arrow;
[09:41] <mdke> mpt: yeah. Perhaps that is out of our scope for this cycle. I thought actually a nice idea would be to put the *whole* switching from windows guide onto the Winfoss install, so that it appears when the livecd is inserted on windows
 automagically gives you the arrows
[09:41] <mpt> which doesn't work solely for menu choices
[09:41] <nixternal> or &arrow;
[09:41] <mpt> but also for navigating through dialogs etc
[09:41] <nixternal> but yeah what mpt just said
[09:41] <mpt> mdke, that's a neat idea
[09:42] <mdke> mpt: I'm going to chat to Henrik if I can find him
Synaptic Package Manager</guimenuitem></menuchoice>
[09:42] <nixternal> that looks about right
[09:43] <nixternal> theCore: planning on using <keywords> in each section?
[09:43] <theCore> nixternal: yep
[09:43] <nixternal> cool
[09:43] <mpt> theCore, so you could have something like <para>In Firefox, choose <guinav>Edit Preferences Security Settings</guinav>
[09:43] <nixternal> i am trying it out with the kde docs, but need something other than htdig
[09:44] <nixternal> is <guinav> something new? i haven't seen that before in docbook
[09:44] <nixternal> or are you using a different dtd?
[09:44] <mpt> ...</para>
[09:44] <mpt> nixternal, we're talking about Mallard :-)
[09:44] <mdke> nixternal: he is trying to contribute to designing a new file format
[09:44] <nixternal> ahhhh
[09:45] <nixternal> why can't you use docbook/xml or sgml?
[09:45] <nixternal> i definitely like the shorter tags though
[09:45] <mpt> because they suck!
[09:45] <nixternal> heh
[09:45] <mpt> or to be more specific:
[09:45] <mpt> http://live.gnome.org/ProjectMallard
[09:45] <theCore> mpt: I like your way
[09:46] <nixternal> so mallard isn't vaporware anymore i take it
[09:46] <mdke> nixternal: no, it still is!
[09:46] <nixternal> mdke: well ya, but i am seeing activity though, which is great
[09:46] <theCore> mpt: but, what about gui buttons?
[09:46] <mpt> nixternal, very very early design stages => vaporware
[09:46] <mpt> theCore,  again
[09:47] <mpt> In my example above, "Settings" *is* a button
[09:47] <theCore> mpt: I like the idea
[09:48] <mpt> I cannot think of a reason to use different elements for labels of different controls, unless you want to style them somehow to look like the controls, but if you did that people would click them by mistake instead of the real controls
[09:48] <mpt> anyway, time for me to exercise and breakfast and stuff, bbl
[09:48] <theCore> hmm... scriptable ...
[09:49] <theCore> nevermind
[09:49] <mpt> If you want actual buttons in help pages, fine, but not with a  element :-)
[09:51] <mdke> ok, we can put the Switching guide in with the winfoss
[09:51] <mdke> that should be pretty great
[10:02] <nixternal> man, the license section of the mallard doc is nuts
[10:07] <mdke> writing their own license is wholly nuts
[10:09] <LaserJock> why is it that they can't use docbook?
[10:09] <mdke> because it's limited to a very stiff <book> or
 structure
[10:09] <mdke> plus, it's tag soup
[10:10] <LaserJock> I haven't quite made the connection from "Our doc system doesn't work well" to "We need a new license and markup language"
[10:10] <mdke> I know the feeling, I posted to their list expressing that very opinion a while back
[10:10] <nixternal> me either LaserJock, but im sure when it is all said and done it will probably make more sense
[10:10] <LaserJock> so for things like TBH were you want to mix-n-match pages
[10:10] <mdke> it's more difficult than it should be
[10:11] <nixternal> which is different than what the freedesktop help standard calls for as well
[10:11] <mdke> still, part of the justification is simply that a paradigm shift will be beneficial to gaining contributors
[10:11] <LaserJock> interesting
[10:11] <LaserJock> sort of like use saying "
[10:12] <LaserJock> "let's use the wiki for docs so the barrier is lower"
[10:12] <mdke> also, a big overhaul gives the chance to do things properly
[10:12] <nixternal> that is very true
[10:13] <nixternal> i hope KDE does something similar for kde4
[10:13] <mdke> they need to get together
[10:13] <nixternal> are we dual licensing still with CC and FDL, or are we CC only now?
[10:14] <nixternal> or do we have 5 licenses now?
[10:14] <nixternal> ;p
[10:14] <mdke> nixternal: you know the answer, but https://wiki.ubuntu.com/DocumentationTeam/License
[10:14] <nixternal> someone just asked me how many licenses were were using now
[10:15] <nixternal> so as i joke i posted his, and then went with the 5 license point
[10:16] <LaserJock> mdke: is it work noting on that page that the Packaging Guide is GPL? I doubt it matter much, but if somebody just grabs the whole repo or something
[10:16] <LaserJock> s/work/worth/
[10:16] <mdke> LaserJock: sure
[10:17] <LaserJock> I hate being the exception, but I don't want to mislead anybody either
[10:17] <nixternal> using the cc-by-sa allows us to incorporate sections of the book, but how does that work if we need to incorporate sections of kde or gnome docs?
[10:18] <nixternal> kde is fdl
[10:18] <mdke> nixternal: we can't incorporate them, but we can link to them
[10:18] <mdke> or supply them as whole documents without modifying the license
[10:19] <nixternal> ya, i figured linking would be the way to go
[10:19] <mdke> we never could incorporate them, as a matter of fact
[10:19] <nixternal> but for something like kubuntu customizing kcontrol and doing system settings instead, is slightly different the kde doc for it, which for us to use would need to be tweaked.
[10:20] <mdke> do a patch on the package which provides the kde doc?
[10:21] <mdke> or fork it and supply it as a separate document in kubuntu-docs
[10:21] <nixternal> well the upstream version will always be different, but ya a fork is what i was thinking, but wasn't sure how the licensing works for it
[10:21] <mdke> you can ship the document, as long as you keep the license notice
[10:21] <nixternal> could i take a fdl document, pull from it bits and pieces as needed, keep an fdl license as well as provide a cc-by-sa license (dual licensing it) and then use it?
[10:22] <nixternal> heh
[10:22] <mdke> no
[10:22] <nixternal> ok
[10:22] <nixternal> kind of acting like a middle man with it, i can only dual license docs that i create then
[10:22] <mdke> or that are already dual licensed
[10:22] <nixternal> ya
[10:23] <nixternal> that's good to know, all of these licenses nowadays will make your head spin
[10:24] <nixternal> muhaha, i can create upstream patches and apply them myself now :)
[10:25] <mpt> mdke, the term "tag soup" doesn't usually mean "far too many element types", it means things like "<foo> <bar> </foo> </bar>"
[10:26] <mdke> nixternal: for relatively small changes, a patch will be the way to go
[10:26] <mdke> mpt: I've changed the definition to be sane
[10:26] <mdke> :(
[10:26] <nixternal> nah mdke, i was referring to that i just received my KDE svn/bug/email package :)
[10:27] <mpt> The Web is famously tag soup, not because there are zillions of elements, but because browsers are resilient in the face of improperly nested elements
[10:27] <mdke> nixternal: I was referring to our earlier conversation about whether to fork or do a patch on the package
[10:27] <nixternal> oh oh
[10:27] <mdke> best to patch the package that provides the document
[10:28] <nixternal> plus easier at the same time
[10:28] <mdke> well, that depends on whether you understand package patch systems
[10:28] <mdke> I guess you do
[10:28] <nixternal> i hope i do
[10:28] <nixternal> otherwise my packages will break computers :)
[10:29] <nixternal> i have 3 months to make MOTU, and the MOTUs seem to be on vacation
[10:30] <mdke> they are just lazy. Get your whip out on LaserJock
[10:30] <nixternal> no doubt
[10:30] <nixternal> thank god for crimsun though, he has helped me out tremendously, although I think I am starting to wear on his nerves
[10:31] <nixternal> RSI break!
[10:34] <LaserJock> nixternal: VACATION!?! ;-)
[11:03] <LaserJock> mdke: does https://wiki.ubuntu.com/DocumentationTeam/License look ok?
[11:06] <mdke> LaserJock: sure
[11:31] <mdke> mpt: I definitely think we can cram quite a lot of the upstream stuff into "Customising your desktop" as a top level topic
[11:32] <mdke> not sure about the explanation of sudo and users/groups
[11:32] <mdke> maybe they fit in there too actually
[11:32] <mdke> will try and knock something out on that before bed
[11:41] <mpt> mdke, users/groups is part of what I intended a top-level "Keeping your computer safe" category for
[11:42] <mpt> * Use a separate account for each user  * Use a firewall  * Lock the computer when you're away from it
[11:42] <mpt> etc
[11:48] <mdke> mpt: that sounds interesting
[11:49] <willvdl> could it make sense to link a topic like that from more than one top-level category?
[11:50] <mdke> willvdl: if appropriate, sure
[11:51] <mpt> One thing I *nearly* did yesterday was include, in the "If you've been using Windows" contents page, a comment about including a list of those questions most commonly asked by people coming from Windows
[11:51] <mpt> which would be a bit different from those questions most commonly asked by people coming from Mac
[11:51] <mpt> etc
[11:51] <mpt> so certainly there can be multiple links to the same topic
[11:51] <mdke> nod
[11:52] <willvdl> hence topic based context really helps I guess
[12:12] <mdke> mpt: what program do you use for editing? It's lovely and tidy
[12:13] <mpt> mdke, gedit
[12:13] <mdke> mpt: really, any special plugins or do you do all that yourself?
[12:14] <mpt> no special plug-ins
[12:14] <mpt> I have a New Year's resolution to teach myself vim
[12:15] <LaserJock> I just use a bit of everything :/
[12:15] <LaserJock> which is probably why my .xml files don't always look consistent
[12:15] <mdke> mpt: so you're wrapping the lines and indenting them yourself? that's very tidy
[12:17] <mpt> It's more paranoia than tidiness
[12:17] <mpt> My room is a mess, but having a messy room doesn't lead to validation errors


[02:44] <xnox> vorlon:  doko: can you please remove dogtag-pki from focal & freeipa? https://bugs.launchpad.net/ubuntu/+source/dogtag-pki/+bug/1858967
[04:04] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.6-1ubuntu1 => 1.3.6-1ubuntu1] (core)
[04:08] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.6-1ubuntu1 => 1.3.6-1ubuntu1] (core)
[04:08] -queuebot:#ubuntu-release- Unapproved: fwupd (focal-proposed/main) [1.3.6-1ubuntu1 => 1.3.6-1ubuntu1] (core)
[05:54] <tjaalton> echoing here..
[05:54] <tjaalton> xnox: the reason why it's not in testing or stable is because openjdk-8 will never migrate. and it works just fine with current nss, and supports tls 1.3 via jss
[05:56] <tjaalton> fedora hasn't moved on from jdk8 yet, which is why jdk11 support hasn't been a top priority. jss and dogtag do now build fine against it, but the rest is still WIP
[08:28] -queuebot:#ubuntu-release- Unapproved: cockpit (eoan-backports/universe) [208-1~ubuntu19.10.1 => 210-1~ubuntu19.10.1] (no packageset)
[08:32] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (eoan-backports) [210-1~ubuntu19.10.1]
[08:32] -queuebot:#ubuntu-release- Unapproved: cockpit (disco-backports/universe) [208-1~ubuntu19.04.1 => 210-1~ubuntu19.04.1] (no packageset)
[08:33] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (disco-backports) [210-1~ubuntu19.04.1]
[08:33] -queuebot:#ubuntu-release- Unapproved: cockpit (bionic-backports/universe) [208-1~ubuntu18.04.1 => 210-1~ubuntu18.04.1] (no packageset)
[08:40] -queuebot:#ubuntu-release- Unapproved: accepted cockpit [source] (bionic-backports) [210-1~ubuntu18.04.1]
[09:08] <jamespage> ahasenack: I think most mojo usage is not via packages tbh
[09:20] <LocutusOfBorg> vorlon, can we please hint cp2k on armhf? regressed in release http://autopkgtest.ubuntu.com/packages/c/cp2k/focal/armhf
[09:21] <LocutusOfBorg> so we might have some scalapack/petsc/slepc/mumps/ and something else migrate
[09:22] <LocutusOfBorg> maybe kicking out sdpa from release pocket until openblas is fixed might help a lot
[10:44] <oSoMoN> firefox is blocked in focal-proposed because of the missing i386 build, I thought this had been dealt with already?
[10:50] <oSoMoN> Laney, vorlon: I noticed there's a duplicate force-badtest entry for firefox/armhf in lp:~ubuntu-release/britney/hints-ubuntu, so one of them should be removed
[10:50] <oSoMoN> and interestingly the last 8 test runs have passed consistently (http://autopkgtest.ubuntu.com/packages/firefox/focal/armhf), so maybe remove both entries?
[10:55] <Laney> okey dokey
[11:15] -queuebot:#ubuntu-release- New binary: python-intervaltree-bio [amd64] (focal-proposed/none) [1.0.1-3.1] (no packageset)
[11:31] -queuebot:#ubuntu-release- New source: pop-gtk-theme (focal-proposed/primary) [5.0.0~1576602011~19.10~7760154~ubuntu1]
[11:32] -queuebot:#ubuntu-release- New source: pop-icon-theme (focal-proposed/primary) [2.1.0~1571158475~19.10~6bf9347~ubuntu1]
[12:12] <oSoMoN> dear SRU team: can someone please review chromium-browser 79.0.3945.79-0ubuntu<IP_ADDRESS> in the eoan queue?
[12:14] <ahasenack> jamespage: looks like IS built their own package, for trusty
[12:15] <ahasenack> at least on wendigo
[12:22] <oSoMoN> vorlon, can you please help unblocking firefox in focal-proposed (blocked by the missing i386 builds)?
[12:27] <jamespage> ahasenack: I think we're only talking about RM'ing for focal development
[12:28] <ahasenack> jamespage: yeah, I'm fine with that, I checked yesterday and updating to 0.11.0 (latest upstream) was annoying, and just fixing the existing old version was annoying as well, it's an old package that has not been rebuilt recently
[12:28] <ahasenack> just copied over from release to release
[12:30] <doko> xnox, vorlon: I see that tjaalton handles these ...
[14:04] -queuebot:#ubuntu-release- Unapproved: fwupd (bionic-proposed/main) [1.2.10-1ubuntu2~ubuntu18.04.2 => 1.2.10-1ubuntu2~ubuntu18.04.3] (desktop-core)
[14:16] -queuebot:#ubuntu-release- New: accepted open-font-design-toolkit [amd64] (focal-proposed) [1.8]
[14:16] -queuebot:#ubuntu-release- New: accepted python-intervaltree-bio [amd64] (focal-proposed) [1.0.1-3.1]
[14:21] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (xenial-proposed/main) [4.4.0-172.202] (core, kernel)
[14:23] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (xenial-proposed) [4.4.0-172.202]
[14:51] <superm1> can someone poke the fwupd in focal unapproved?  I'm hoping it sorts out the transient autopkgtest failures that have been preventing migration.
[14:53] -queuebot:#ubuntu-release- Unapproved: cinder (eoan-proposed/main) [2:15.0.0-0ubuntu1 => 2:15.0.1-0ubuntu1] (openstack, ubuntu-server)
[14:53] -queuebot:#ubuntu-release- Unapproved: octavia (eoan-proposed/universe) [5.0.0-0ubuntu1 => 5.0.1-0ubuntu1] (no packageset)
[14:53] -queuebot:#ubuntu-release- Unapproved: neutron (eoan-proposed/main) [2:15.0.0-0ubuntu1 => 2:15.0.1-0ubuntu1] (openstack, ubuntu-server)
[15:10] <seb128> superm1, hey, happy new year!
[15:10] <seb128> superm1, ^
[15:10] <seb128> superm1, ups, I though the bot showed that but I accepted them now
[15:10] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [amd64] (focal-proposed) [1.3.6-1ubuntu1]
[15:10] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [armhf] (focal-proposed) [1.3.6-1ubuntu1]
[15:11] -queuebot:#ubuntu-release- Unapproved: accepted fwupd [arm64] (focal-proposed) [1.3.6-1ubuntu1]
[15:31] <seb128> can someone ignore the openjdk-13/14 armhf autopkgtest failures for libglvnd? those are clearly not due to that lib, just not working more often than not and taking ages when they do work still
[16:08] <vorlon> LocutusOfBorg: where do you see that it has regressed in release? http://autopkgtest.ubuntu.com/packages/c/cp2k/focal/armhf shows failures for the -proposed version only
[16:08] <vorlon> LocutusOfBorg: I have been working on this transition, cp2k is the problematic one because the regression happens as a result of the Debian changes
[16:09] <vorlon> oSoMoN: not blocked by missing build but by failing autopkgtest; I'll hint it now
[16:12] <superm1> seb128: happy new year to you too.  great thanks!
[16:16] <ddstreet> vorlon i see ubuntu-distro-info lists next friday as the final day for Disco, but i havent' seen any reminder email yet, is that day correct or will disco eol later in the month?
[16:18] <vorlon> infinity: ^^
[16:23] <infinity> ddstreet, vorlon: Ahh, yeah, the notice should have gone out when we were all still on holidays to make that date.  I'll send it today, and it'll be today + 14 days.
[16:23] <ddstreet> thnx!
[16:23] <LocutusOfBorg> 6.1-3build1 	cp2k/6.1-3build1 	2020-01-05 06:34:12 UTC 	1h 29m 05s 	vorlon 	fail 	log   artifacts
[16:23] <LocutusOfBorg> vorlon, ^^
[16:23] <LocutusOfBorg> oh got it
[16:23] <LocutusOfBorg> meh
[16:24] <LocutusOfBorg> a nasty guy might want to sync cp2k from experimental
[16:41] <oSoMoN> vorlon, thanks
[16:47] <vorlon> LocutusOfBorg: given that many of the test regressions seem to be due to changes to what version of libint is linked against, probably not
[16:52] -queuebot:#ubuntu-release- New binary: plymouth [s390x] (focal-proposed/main) [0.9.4git20200109-0ubuntu1] (core)
[16:53] -queuebot:#ubuntu-release- New binary: plymouth [ppc64el] (focal-proposed/main) [0.9.4git20200109-0ubuntu1] (core)
[16:55] -queuebot:#ubuntu-release- New binary: plymouth [arm64] (focal-proposed/main) [0.9.4git20200109-0ubuntu1] (core)
[16:58] -queuebot:#ubuntu-release- New binary: linux-signed [amd64] (eoan-proposed/main) [5.3.0-27.29] (core, kernel)
[16:58] -queuebot:#ubuntu-release- New binary: linux-signed [s390x] (eoan-proposed/main) [5.3.0-27.29] (core, kernel)
[16:58] -queuebot:#ubuntu-release- New binary: linux-signed [ppc64el] (eoan-proposed/main) [5.3.0-27.29] (core, kernel)
[16:59] -queuebot:#ubuntu-release- New binary: linux-signed [arm64] (eoan-proposed/main) [5.3.0-27.29] (core, kernel)
[17:03] -queuebot:#ubuntu-release- New binary: plymouth [armhf] (focal-proposed/main) [0.9.4git20200109-0ubuntu1] (core)
[17:29] -queuebot:#ubuntu-release- New: accepted linux-signed [amd64] (eoan-proposed) [5.3.0-27.29]
[17:29] -queuebot:#ubuntu-release- New: accepted linux-signed [ppc64el] (eoan-proposed) [5.3.0-27.29]
[17:29] -queuebot:#ubuntu-release- New: accepted linux-signed [arm64] (eoan-proposed) [5.3.0-27.29]
[17:29] -queuebot:#ubuntu-release- New: accepted linux-signed [s390x] (eoan-proposed) [5.3.0-27.29]
[17:31] -queuebot:#ubuntu-release- New binary: dpdk [ppc64el] (focal-proposed/main) [19.11-2ubuntu1] (ubuntu-server)
[17:43] -queuebot:#ubuntu-release- New binary: dpdk [armhf] (focal-proposed/main) [19.11-2ubuntu1] (ubuntu-server)
[17:54] <ahasenack> did the excuses page break, or is it just taking longer to process all the data? Timestamp is Generated: 2020.01.09 15:18:56 +0000
[17:54] <ahasenack> that's over 2h ago
[17:56] <RikMills> ahasenack: proposed migration runs have been failing with: "FATAL: Failure to fetch swift results from ...."
[17:57] <RikMills> current one is still going so fingers crossed
[17:57] <ahasenack> oh
[17:57] <RikMills> damn. that crashed
[17:57]  * RikMills jinxed it
[17:58] <ahasenack> so canonistack issue?
[17:59] <RikMills> Laney cjwatson? ^
[17:59] <cjwatson> RikMills: autopkgtest isn't me
[18:00] <RikMills> sorry. hard to keep track of who pushes buttons on what!
[18:00] -queuebot:#ubuntu-release- New binary: dpdk [amd64] (focal-proposed/main) [19.11-2ubuntu1] (ubuntu-server)
[18:01] <Laney> I'll ask IS but I can't really stick around
[18:01] <ahasenack> RikMills: where did you see that error?
[18:02] <Laney> https://people.canonical.com/~ubuntu-archive/proposed-migration/log/focal/2020-01-09/
[18:02] <Laney> worth bookmarking
[18:02] <ahasenack> til
[18:04] <ahasenack> thanks, and thanks for checking with #is
[18:05] <Laney> OK it's being looked into, maybe vorlon can update this channel when there's an outcome
[18:05] <Laney> o/
[18:06] <vorlon> ack
[18:21] -queuebot:#ubuntu-release- New: accepted dpdk [amd64] (focal-proposed) [19.11-2ubuntu1]
[18:21] -queuebot:#ubuntu-release- New: accepted dpdk [ppc64el] (focal-proposed) [19.11-2ubuntu1]
[18:21] -queuebot:#ubuntu-release- New: accepted plymouth [armhf] (focal-proposed) [0.9.4git20200109-0ubuntu1]
[18:21] -queuebot:#ubuntu-release- New: accepted plymouth [s390x] (focal-proposed) [0.9.4git20200109-0ubuntu1]
[18:21] -queuebot:#ubuntu-release- New: accepted dpdk [armhf] (focal-proposed) [19.11-2ubuntu1]
[18:21] -queuebot:#ubuntu-release- New: accepted plymouth [ppc64el] (focal-proposed) [0.9.4git20200109-0ubuntu1]
[18:21] -queuebot:#ubuntu-release- New: accepted plymouth [arm64] (focal-proposed) [0.9.4git20200109-0ubuntu1]
[18:53]  * infinity side-eyes nova, and wonders why it's suddenly trying to pull a different netcat implementation into main.
[18:54] <vorlon> infinity: because it's the one that still exists on i386 (it's an arch: all package)
[18:54] <infinity> Well, maybe not "suddenly".  Seems the release pocket has this oddity too.
[18:54] <infinity> vorlon: Oh.  That makes more sense.  And ick.
[18:55] <infinity> vorlon: Was just going through c-m/c-m-p, didn't think to apply a "lol i386" filter to it.
[18:55] <vorlon> :)
[18:55] <infinity> vorlon: Plans to remove nova/i386 or resurrect netcat-openbsd/i386?
[18:56] <vorlon> infinity: problem is, nova is *also* arch: all
[18:56] <infinity> Oh.  More ick.
[18:56] <vorlon> not sure if marking nova as seeded only on !i386 would help
[18:57] <vorlon> or just make germinate grow a hand so it can hold the knife to stab me
[18:57] <infinity> It won't.
[18:59] <infinity> vorlon: Resurrecting netcat-openbsd/i386 doesn't seem like it'd be super awful.
[18:59] <infinity> Only deps are libc6 and libbsd0 (which seems to still exist on i386 for now)
[19:00] <vorlon> infinity: ok.  add it to the seed and resurrect?
[19:00] <infinity> Will do.
[19:01] <Kamilion> Busy testrolling my focal iso, went to install squid-deb-proxy-client, it wanted to pull in py2, so I threw half an hour at bringing it to py3. Patch sent to mvo@debian, I'll leave it here too. https://files.sllabs.com/files/storage/code/ubuntu/apt-avahi-discover.p3.patch
[19:03] <rbasak> Nice, thanks!
[19:04] <vorlon> infinity: oh also since netcat-openbsd had an upload after the filter went into effect, looks like the resurrect requires a manual packageset tweak plus a no-change rebuild :P
[19:05] <infinity> vorlon: Yes to the first, no to the second (I have magic powers).
[19:05] <vorlon> hngh ok
[19:06] <vorlon> infinity: anyway I've addded it to the packageset for you
[19:06] <infinity> vorlon: Shiny, then I shall magically power it.
[19:08] <infinity> 2020-01-09 19:08:01 INFO    Considering netcat-openbsd 1.206-1 in focal
[19:08] <infinity> 2020-01-09 19:08:01 INFO    Created 1 build(s)
[19:11] <infinity> vorlon: And re-published the release pocket version in case the proposed one gets stuck.
[19:12] <infinity> s/gets/stays/ ..
[19:18]  * infinity removes linux-oem-osp1 with extreme prejudice now that the meta is transitioned.
[19:22] -queuebot:#ubuntu-release- Packageset: Added netcat-openbsd to i386-whitelist in focal
[20:27] <Eickmeyer> I see nobody has taken a look at lv2vst in NEW yet? This is part of a backup plan in case Hydrogen doesn't release a 1.0 in time for Focal so that we can change our manual ISO QA tests if necessary.
[20:28] <Eickmeyer> Basically, I need this ASAP as its a build-dep for another package we need (avldrums.lv2).
[20:37] -queuebot:#ubuntu-release- New binary: sight [amd64] (focal-proposed/universe) [19.0.0-4] (no packageset)
[21:01] <vorlon> I didn't get any specific updates from IS, but I see that the latest p-m run has cleared the swift problems of before
[21:02] <RikMills> :)
[21:50] <vorlon> infinity: I don't see your netcat-openbsd/i386 binaries in either pocket yet, do you know if there've been publisher problems?
[21:53] <vorlon> first time I've ever had syncpackage -f fail complaining that it can't verify the gpg signature on the source package. :/ is that a question of out-of-date debian-keyring on the client OS?
[21:53] <vorlon> and I see no option to skip verification
[21:54] <vorlon> (package is libfastahack, client OS is eoan)
[21:55] <vorlon> works if I run syncpackage from focal
[21:58] <mfo> Question on apparent SRU corner case.  A package has a bug when running in the v5.3 kernel. Thus it needs fixing in Eoan and Bionic (for the HWE kernel).  Does Disco (regardless of time-to-EOL at this point) which runs the v5.0 kernel thus not affected, needs the patches too, for the only reason that they're being introduced in an earlier release (Bionic), and the rule is that all later releases should have the fixes too?
[22:01] <mfo> Other question is obviously, now considering Disco time-to-EOL, must it get not-too-serious-impact fixes now (e.g, case above), given that -proposed takes 7+ days, and it has ~14 left?  Not a problem uploading it, just want to make not spending other reviewers/sru-team time.
[22:01] <mfo> s/make not/make sure I'm not/
[22:02] <infinity> vorlon: https://launchpad.net/ubuntu/focal/i386/netcat-openbsd
[22:03] <infinity> vorlon: Things are slow, but getting there.
[22:03] <vorlon> yeah, was wondering about the "are slow" part
[22:04] <infinity> Thu, 09 Jan 2020 18:07:13 +0000: Triggering archive.syncproxy.ubuntu.com:
[22:04] <infinity> Thu, 09 Jan 2020 18:07:13 +0000: Triggering ports.syncproxy.ubuntu.com:
[22:04] <infinity> Thu, 09 Jan 2020 20:40:33 +0000: Triggering archive.syncproxy.ubuntu.com:
[22:04] <infinity> Thu, 09 Jan 2020 20:40:34 +0000: Triggering ports.syncproxy.ubuntu.com:
[22:04] <vorlon> mfo: don't bother with disco
[22:04] <infinity> Thu, 09 Jan 2020 21:54:02 +0000: Triggering archive.syncproxy.ubuntu.com:
[22:04] <infinity> Thu, 09 Jan 2020 21:54:03 +0000: Triggering ports.syncproxy.ubuntu.com:
[22:04] <infinity> There are a few very long runs in a row.  Current one's not super quick either.  Should be clearing up, I hope.
[22:05] <vorlon> mfo: because of the timing.  This does make me wonder however what we do for users who have installed the HWE kernel on bionic, then configure do-release-upgrader for non-LTS upgrades and then upgrade to disco
[22:06] <vorlon> since the linux-hwe metapackage doesn't exist at all in non-LTS releases currently
[22:06] <mfo> vorlon, yeah, ddstreet and I were wondering about that too.
[22:06] <vorlon> I guess this means a user who has installed the hwe kernel - which is the default for some install media starting with the .2 point release - wind up with no kernel support after upgrade
[22:06] <vorlon> bdmurray: ^^ do you know of any release-upgrader handling to the contrary?
[22:07] <mfo> vorlon, for now, I was most curious if there's anything set in stone that later releases should have the patches introduced in earlier releases, even if not affected, for whatever reason/policy.
[22:07] <mfo> say, if a similar case pops up in the future.
[22:07] <mfo> for a release that would take longer to EOL :)
[22:08] <vorlon> mfo: the rule is that if you fix a bug in one release, it shouldn't regress for the user when they upgrade to a later release
[22:08] <infinity> vorlon: I feel like Andy and I have discussed this in the past, and the plan was for LTS+1 and beyond to have the meta revert hwe-XX.XX to generic, but I'm not sure if that ever happened past discussion.
[22:08] <infinity> vorlon: It absolutely is not the release upgrader's job to get that right, IMO.
[22:09] <vorlon> infinity: well, linux-image-generic-hwe-18.04 exists only in bionic and focal
[22:09] <infinity> Right, so that never got past the discussion stage, apparently. :P
[22:09] <infinity> Could still be fixed in eoan if we cared.  Or we could turn over a new leaf for 20.10 and beyond.
[22:12] <apw> infinity, i believe that those transition to -generic in focal
[22:12] <mfo> vorlon, right, that I know. but in this case (ignoring for a moment the possibility of ending up with a v5.3 kernel in Disco via Bionic upgrade), where there's no 'regression' possible bcz the supported configuration does not allow it to happen.   I guess the question is,  is this a rule based on 'make sure the code is applied, regardless'  or on 'avoid regressions where they can happen' (on the supported configurations).
[22:12] <infinity> apw: They sure do.  But the point is that they should do so earlier as well, for people upgrading to interim releases from .2 through .4
[22:12] <infinity> apw: And I thought we'd planned on that, but maybe it's all in my head.
[22:13] <infinity> mfo: The rule is avoid regressions, not pointlessly copy and paste dead code.
[22:13] <apw> infinity, hmm yes, we might have intended to do that
[22:13] <mfo> infinity, alright, that phrases it pretty well.
[22:14] <mfo> vorlon, infinity: thanks
[22:16] <infinity> vorlon: Looks like all things Soyuz have been gummed up by chubby security releases.  I *think* the current cycle in progress should be the last long one.
[22:17] <infinity> Maybe.
[22:17] <wgrant> process-build-uploads is sluggish atm due to some KDE stuff
[22:20] <infinity> Ahh, yes, there's also that.  Which was why my build took 37 years to "upload".
[22:20] <infinity> But I was strictly looking at publisher timings here.
[22:20] <infinity> Which is currently firefox security (and other misc).
[22:21] <cjwatson> Also long backlog from network trouble I think
[22:22] <infinity> The best solution is to stop watching the log and to start driving to the taco place.
[22:22] <wgrant> Definitely.
[22:33] <vorlon> doko: I've had a look now at the specifics of the gcc-9/i386 autopkgtest failures.  it's an interesting case, of course the autopkgtest wants to install the i386 gcc, but because my autopkgtest cross patch uses apt-get build-dep, we're stuck because apt-get also enforces that the build-essential package be installed despite this not being declared anywhere... and of course gcc-9:i386 conflicts with
[22:33] <vorlon> a dependency of build-essential.  I wonder if juliank has thoughts on apt-get build-dep --without-build-essential
[22:51] <infinity> vorlon: A cross apt-get build-dep should install the right cross-build-essential, ideally.  Not sure if it knows how to do that and, if so, not sure you'd be calling it in a way that would do so.
[22:51] <infinity> I think last time we did mass cross-building, that hack was in sbuild, not apt.
[22:52] <vorlon> infinity: we are calling apt-get build-dep -a arch
[22:52] <vorlon> it still enforces build-essential in addition to crossbuild-essential-arch
[22:52] <infinity> That doesn't seem right.  Should be one or the other, I'd think, not both.
[22:54] <infinity> Or maybe it is right.  It's been a while since I walked those twisty cross-build roads.
[22:54] <infinity> I guess cross does want HOSTCC and BUILDCC to both exist for $reasons, so maybe having both build-essentials is correct.
[23:59] -queuebot:#ubuntu-release- Unapproved: openssh (eoan-proposed/main) [1:8.0p1-6build1 => 1:8.0p1-6ubuntu0.1] (core)


[12:20] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4691 Preparing packages
[12:26] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4691 Abandoning ticket
[12:27] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4691 Preparing packages
[12:29] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4692 Preparing packages
[12:40] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4693 Preparing packages
[12:52] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4691 Failed to build
[13:54] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4693 Successfully built
[14:14] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4693 Pending binary packages
[14:34] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4693 Successfully built
[15:33] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4692 Successfully built
[15:43] -queuebot:#ubuntu-ci-eng- mitya57, https://bileto.ubuntu.com/#/ticket/4690 Preparing packages
[15:53] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4692 Pending binary packages
[17:05] -queuebot:#ubuntu-ci-eng- Laney, https://bileto.ubuntu.com/#/ticket/3762 Failed setting processors!
[17:25] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4691 Preparing packages
[17:31] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2351 Needs rebuild due to new commits (vivid/ubuntu-keyboard). Ready to build (/:, vivid/Failed, vivid/cache., vivid/local, vivid/lp:ubuntu-keyboard/vivid, vivid/to, vivid/update)
[17:56] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4692 Needs rebuild due to new commits
[18:07] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4692 Preparing packages
[18:11] -queuebot:#ubuntu-ci-eng- mitya57, https://bileto.ubuntu.com/#/ticket/4690 Uploading build
[18:13] -queuebot:#ubuntu-ci-eng- Elleo, https://bileto.ubuntu.com/#/ticket/2351 Ready to build (/:, vivid/Failed, vivid/cache., vivid/local, vivid/lp:ubuntu-keyboard/vivid, vivid/to, vivid/update). Successfully built (vivid/ubuntu-keyboard)
[18:31] -queuebot:#ubuntu-ci-eng- mitya57, https://bileto.ubuntu.com/#/ticket/4690 Pending binary packages
[18:33] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4692 Pending binary packages
[20:14] -queuebot:#ubuntu-ci-eng- jamespage, https://bileto.ubuntu.com/#/ticket/4054 Needs rebuild due to higher version at destination (bionic/ceph). Ready to build (bionic/boost1.74, bionic/nova, bionic/openvswitch, bionic/ovn, bionic/python-django-compressor, bionic/python-oslo.metrics)
[21:12] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4691 Pending binary packages
[23:12] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4691 Successfully built
[23:14] -queuebot:#ubuntu-ci-eng- 3v1n0, https://bileto.ubuntu.com/#/ticket/4692 Successfully built
[23:31] -queuebot:#ubuntu-ci-eng- mitya57, https://bileto.ubuntu.com/#/ticket/4690 Successfully built