[01:56] <^barry^> hello
[01:57] <^barry^> anyone know how to connect my ubuntu touch to my ubuntu desktop?
[02:26] <dobey> ^barry^: connect how? if you plug it in, it shows up as an MTP device.
[02:36] <pdxwebdev> What is the menu called where you swipe downward and you get scrollable tabs saying 'battery' 'network' 'upcoming events' etc. is that the indicator menu?
[02:36] <dobey> yes
[02:37] <pdxwebdev> If I wanted to add another tab, which package would I edit?
[02:38] <dobey> whatever one you create that adds an indicator
[02:39] <pdxwebdev> I know about .desktop files and .settings files. does adding an indicator menu tab work similarly?
[02:40] <pdxwebdev> I guess I'm just lost on how to even go about affecting indicator menu in any way.
[03:19] <dobey> pdxwebdev: i don't know exactly, but i'm pretty sure that "adding indicators from your app" is not part of the sdk, and there is no intention to allow additional indicators
[03:20] <dobey> iow, the notification icons is one of the huge problems on android, and the design we have for ubuntu is to try and avoid getting into that situation
[03:22] <pdxwebdev> understandable.
[03:23] <pdxwebdev> I think i'm looking to add a system indicator, not an app indicator
[03:23] <dobey> what kind of indicator?
[03:23] <pdxwebdev> I'm prototyping an authentication framework to be used on the entire phone
[03:24] <pdxwebdev> So I'm trying to add a new tab to the indicator menu along side the "transfers" "network" etc.
[03:24] <dobey> it would help when developing stuff, to not think of it as explicitly "for the phone" as such, given we are pushing toward a converged system
[03:24] <pdxwebdev> This is something that would be baked into the OS, not an app you would download
[03:25] <dobey> pdxwebdev: i'd suggest talking to security and design about what you want to do then
[03:25] <pdxwebdev> I have been in contact with them and they requested a demo. So I'm just trying to put something together for them to look at.
[03:26] <pdxwebdev> To see if they would be interested.
[03:26] <dobey> personally, i'd suggest that an indicator is probably the wrong solution for whatever it is you want to do with the indicator
[03:27] <dobey> (there are too many indicators already, really)
[03:29] <pdxwebdev> I agree, but I do what to offer the user a quick way to  access this feature.
[03:29] <pdxwebdev> As far as I can tell, the indicator pull down menu appears to be the fastest/most convenient
[03:30] <pdxwebdev> I'm open to suggestions, however.
[03:31] <dobey> well considering i have no idea wha tthe "feature" is exactly, i can't really suggest anything :)
[03:31] <pdxwebdev> it would be a qr scanning mechanism used for authentication.
[03:31] <pdxwebdev> So a web site presents a qr code. you scan it to sign in or register.
[03:32] <dobey> presents the qr code where?
[03:33] <pdxwebdev> on the site itself, instead of presenting a login or registration form, it presents a qr code. you scan that from your phone and poof, ur in.
[03:34] <pdxwebdev> I wanted to place this in the indicator area due to the likelyhood of frequent use.
[03:34] <dobey> that doesn't sound very secure or user-friendly to me, but it sounds like the place where you should be implementing something is in the browser itself.
[03:34] <pdxwebdev> It's difficult to explain.
[03:36] <dobey> the qr code is a second factor auth metchanism? so the user would scan the code presented on their pc, with the phone?
[03:37] <pdxwebdev> correct
[03:38] <pdxwebdev> It's very secure, when you compare it with username/password auth
[03:38] <dobey> sounds like it should just be an app, and if a user uses a web site that uses such a method, they can pin that app to their launcher for quick access
[03:38] <pdxwebdev> right, but what about authenticating for apps on the phone?
[03:39] <dobey> then they'll need another phone i guess, to scan the qr code. otherwise it's not exactly a second factor auth mechanism
[03:40] <pdxwebdev> sorry, I overlooked the 'second factor' statement. it would be single factor
[03:40] <dobey> oh
[03:41] <pdxwebdev> the qr scanning would be enough.
[03:41] <dobey> then like i said before, the place to implement it would be the browser itself
[03:42] <pdxwebdev> I'm implementing a portable identity.
[03:42] <dobey> but i also think it's not very secure or user-friendly
[03:42] <pdxwebdev> To auth inside and outside of the phone.
[03:43] <pdxwebdev> Implementing in the browser would leave the user's identity in the browser.
[03:43] <dobey> implementing in the browser is the only way to get the qr code out of the browser. unless you require users to have a second phone
[03:44] <pdxwebdev> oh, yeah, I have another mechanism for that.
[03:44] <dobey> or at least a mirror or usb-otg webcam or something
[03:46] <pdxwebdev> It's clear to me that this needs to be below the app layer. I've already added an extra step to the welcome wizard, an icon in system settings, and now the last piece is the indicator menu.
[03:46] <pdxwebdev> So I'll keep digging.
[03:49] <dobey> i don't understand why there needs to be anything at the system layer for this. nothing needs to be in the welcome wizard for logging into a random web site that might implement this auth scheme.
[03:51] <pdxwebdev> It's an identity management layer. basically turning your phone into the host of your social network.
[03:51] <pdxwebdev> giving social structure to your contacts
[03:52] <pdxwebdev> other features as well
[03:52] <dobey> and what if i lose my phone in a taxi or something?
[03:54] <dobey> just doesn't seem practical to me *shrug*
[03:54] <dobey> anyway, late here, so i should go
[03:54] <pdxwebdev> there are challenges. the cloud isn't perfect either.
[03:56] <pdxwebdev> thanks for you suggestions. I'll keep trucking ;)
[06:35] <rigved> hi everyone
[06:35] <rigved> how will ubuntu touch be supported on the nexus 7 2013 version? any plans released?
[06:35] <rigved> *how long
[09:38] <oSoMoN> is it a known issue that the name "HERE" is incorrectly translated to French in the location indicator pulldown menu?
[09:39] <ogra_> oSoMoN, there was a translation hint added very recently
[09:39] <ogra_> https://launchpad.net/ubuntu/utopic/+source/ubuntu-system-settings/0.3+14.10.20140925-0ubuntu1
[09:39] <oSoMoN> ok, so it’s just a matter of fixing the existing translations, then
[09:40] <ogra_> seems thats bug 1368838
[09:43] <jibel> oSoMoN, I already fixed the string and the French team reviewed it
[09:43] <oSoMoN> jibel, excellent!
[09:43] <jibel> oSoMoN, we need a new export of the lang pack I guess
[09:43] <JamesTait> Good morning all; happy Monday, and happy Ecological Debt Day! :-D
[10:26] <tetraquark1> Я здесь: Praha 6, Чехия
[10:39] <mpt> Well, that was weird. I connected my phone to my PC to charge, and it got into an endless loop of restarting the phone every ~30 seconds, and “Unable to mount Android” and “Unable to mount Nexus 4” errors on the PC
[10:40] <mpt> Got out of it by connecting the phone directly to power instead
[11:07] <mardy> dednick: hi! Is there a way to know if a given PID has a mir connection open (what I need to know, is if I can open a trust session having this PID as initiator)?
[11:07] <dednick> mardy: from an external process? no.
[11:08] <dednick> mardy: best to ask in #unity-mir though. i'm not 100%
[11:08] <dednick> #ubuntu-mir i mean
[11:08] <dednick> mardy: ^
[11:10] <mardy> dednick: thanks, I'll ask there too
[11:12] <mardy> t1mp: do you know the answer to this (or do you know who could know)? http://askubuntu.com/questions/532516/how-to-change-the-font-style-of-a-listitem
[11:36] <t1mp> mardy: I answered the question on https://askubuntu.com/questions/532516/how-to-change-the-font-style-of-a-listitem/532796#532796
[11:36] <t1mp> mardy: unfortunately it doesn't help you much :(
[11:38] <mardy> t1mp: that's anyway informative, thanks
[11:38] <t1mp> mardy: if you look at the code of, for example, SingleValue, you will see that it is relatively simple
[11:39] <nerochiaro> jhodapp: hi, I'm trying to see signals from the hub on DBUS, but i only see the ones on the org.mprisMediaPlayer2.Player interface. I don't see any from the hub itself. Shouldn't it use the com.ubuntu.media.Player interface ?
[11:39] <t1mp> mardy: you could copy that code (and copy LabelVisual as well) as a base for your own component, if you decide to do that
[11:39] <jhodapp> nerochiaro, hey there, you're looking on the session bus right?
[11:40] <nerochiaro> jhodapp: yes, i assume dbus-monitor uses that by default
[11:41] <jhodapp> nerochiaro, I forget, but you can specify it with --session
[11:42] <nerochiaro> jhodapp: ok, confirmed with --session
[11:43] <jhodapp> nerochiaro, confirmed the same thing or you can see the signals you need to see?
[11:43] <nerochiaro> jhodapp: dbus-monitor --session "type=signal" | grep -i media doesn't get any signal that is not from MPRIS
[11:44] <nerochiaro> jhodapp: and from what i can see from the hub sources it should use another interface. is that correct ?
[11:44] <jhodapp> nerochiaro, have you tried without a filter? you should definitely at least see a position retrieval periodically when playing media
[11:44] <jhodapp> nerochiaro, yeah it does
[11:45] <nerochiaro> jhodapp: on what interface ?
[11:46] <jhodapp> nerochiaro, forget offhand, let me look at the code
[11:50] <jhodapp> nerochiaro, core.ubuntu.media.Service.Player
[11:52] <mardy> Mirv: I added you as reviewer for https://code.launchpad.net/~mardy/ubuntu-system-settings-online-accounts/lp1342031/+merge/237244, when you have a minute
[11:54] <nerochiaro> jhodapp: so dbus-monitor --session "type=signal,interface='core.ubuntu.media.Service.Player'" shows signals for you when you play a video in mediaplayer-app ?
[11:54] <jhodapp> nerochiaro, I've not tried any filtering before
[11:55] <jhodapp> nerochiaro, have you tried without any filtering?
[11:56] <nerochiaro> jhodapp: yes, dbus-monitor --session | grep Player | grep ubuntu doesn't show anything (i can't really do without grep, there is too much noise on the bus)
[11:56] <jhodapp> nerochiaro, try without a grep once, see if you get Position back while playing music
[11:57] <nerochiaro> jhodapp: ok, i'll pipe it to less and look manually through the noise. but it's a good way to miss stuff
[11:57] <nerochiaro> jhodapp: grep seems more reliable than my eyes
[11:57] <jhodapp> nerochiaro, yes indeed, I just want to ensure that you're getting something
[11:58] <jhodapp> nerochiaro, then we can try a filter
[11:59] <nerochiaro> jhodapp: btw, i'm playing videos,not music, does that make a difference ?
[11:59] <jhodapp> nerochiaro, well for this test try music, should produce the least amount of noise
[12:03] <nerochiaro> jhodapp: playing music i get a lot of method call sender=:1.176 -> dest=core.ubuntu.media.Service serial=125 path=/core/ubuntu/media/Service/sessions/0; interface=org.freedesktop.DBus.Properties; member=Get
[12:03] <nerochiaro>    string "org.mpris.MediaPlayer2.Player"
[12:03] <nerochiaro>    string "Position"
[12:04] <jhodapp> nerochiaro, yes, so that's correct
[12:04] <jhodapp> nerochiaro, so now you've verified the interface
[12:05]  * jhodapp brb
[12:08] <nerochiaro> jhodapp: ok, let's take a step back. what I'm trying to understand is what is behind AalMediaPlayerService::core::ubuntu::media::Player::set_playback_complete_callback in terms of DBUS signals
[12:09] <nerochiaro> jhodapp: in other words, what is the signal we are attaching in qtubunt-media that comes from media-hub to signal the end of playback
[12:09] <nerochiaro> ?
[12:20] <jhodapp> nerochiaro, right, try watching for that with music once
[12:20] <jhodapp> nerochiaro, it'll be easier to see
[12:20] <nerochiaro> jhodapp: i don't get it
[12:20] <jhodapp> nerochiaro, let me see if I can catch it for you
[12:35] <nerochiaro> jhodapp: caught it ?
[12:35] <jhodapp> nerochiaro, not yet, having an issue with media-hub on one device, trying the other
[12:41] <jhodapp> nerochiaro, ok, got it
[12:41] <jhodapp> nerochiaro, let me pastebin it
[12:44] <jhodapp> nerochiaro, http://pastebin.ubuntu.com/8507140
[12:45] <jhodapp> nerochiaro, EndOfStream
[12:47] <nerochiaro> jhodapp: ok, i wouldn't have guessed that that signal mapped to playback_complete. where in the code you see that ? (so that i don't have to ask these kind of questions again in the future wasting everyone's time)
[12:48] <jhodapp> nerochiaro, it's no problem to ask, happy to help
[12:48] <jhodapp> nerochiaro, one sec
[12:49] <jhodapp> nerochiaro, you're wondering where in qtubuntu-media this gets mapped?
[12:50] <nerochiaro> jhodapp: yes
[12:52] <jhodapp> nerochiaro, look in aalmediaplayerservice.cpp:77
[12:55] <nerochiaro> jhodapp: what i see there is the point where qtubuntu-media connects to a callback called "playback_complete", but how do you know that playback_complete maps to the EndOfStream signal from DBUS ?
[12:55] <jhodapp> nerochiaro, because of the media-hub-client
[12:55] <jhodapp> nerochiaro, player_stub.cpp
[12:57] <jhodapp> nerochiaro, the m_hubPlayerSession->set_playback_complete_callback() is calling the media-hub client library
[12:57] <nerochiaro> jhodapp: ok, that was the piece i was missing
[12:57] <nerochiaro> jhodapp: the split of the hub between the server and a client lib
[12:57] <jhodapp> exactly
[12:58] <jhodapp> nerochiaro, just keep asking questions, I've looked at this a lot so I'm not sure what's not obvious anymore :)
[13:01] <nerochiaro> jhodapp: will do. thanks
[13:01] <jhodapp> np
[13:17] <nerochiaro> jhodapp: so I think the problem I was chasing last week seems to be rooted in the fact that the EndOfStream signal is on the bus, but the client library doesn't seem to receive it
[13:23] <gatox> kenvandine, hi, can i ask you for a review here: https://code.launchpad.net/~diegosarmentero/ubuntu-system-settings/display-errors/+merge/235037 - https://code.launchpad.net/~diegosarmentero/ubuntu-system-settings/account-detected/+merge/236313
[13:24] <jhodapp> nerochiaro, ok, it'd be interesting to put a debug output on the EndOfStream signal emission (server side) and on the client side
[13:24] <kenvandine> gatox, sure
[13:24] <gatox> kenvandine, thx
[13:25] <nerochiaro> jhodapp: i did that last week, and the client side doesn't get received. since i see it on the bus, i assume the debug output if I put it on the emission will be there
[13:25] <nerochiaro> jhodapp: i mean, there's no debug printout on the client side
[13:26] <jhodapp> nerochiaro, now that's interesting
[13:26] <jhodapp> nerochiaro, might want to ask tvoss about that since it's using dbus-cpp
[13:27] <jhodapp> nerochiaro, might be a dbus-cpp bug
[13:27] <jhodapp> nerochiaro, perhaps a race condition
[13:27] <nerochiaro> jhodapp: it doesn't happen all the time, just when i destroy the Video component in QML and recreate it
[13:27] <jhodapp> nerochiaro, yes, sounds perhaps like a race condition indeed
[13:35] <brendand> jgdx, i need to confirm one more bug fix then i'll try to see if i can find some repro steps
[13:35] <jgdx> brendand, cool, thanks
[13:35] <brendand> jgdx, maybe it has something to do with connecting from the wizard?
[13:36] <jgdx> brendand, I can repro it consistenly by forgetting the currently connected one.
[13:36] <jgdx> not sure the wizard is involved, it's pretty generic stuff (networkmanager)
[13:37] <brendand> jgdx, yeah but just now i tried having created a new connection and it didn't work
[13:37] <brendand> i mean it did work :)
[13:37] <jgdx> err ;:p
[13:37] <jgdx> kenvandine, that silo stops my krillin from bootin'
[13:37] <jgdx> kenvandine, 20
[13:37] <jgdx> is weird
[13:38] <kenvandine> weird
[13:40] <jgdx> brendand, you created a new connection, and when you entered previous networs you were connected to it. Forgetting it brought you back to previous or wifi?
[13:42] <brendand> jgdx, yeah if you forget the network you are connected to then it goes to wifi, otherwise previous networks
[13:43] <brendand> jgdx, i can either file a bug or you can rework the silo
[13:43] <brendand> jgdx, not sure which one is faster
[13:43] <mterry> kenvandine, if you have time for https://code.launchpad.net/~mterry/ubuntu-system-settings/wizard-refresh-take-6/+merge/235720 today, I will give you a virtual hug
[13:44] <jgdx> brendand, what ever you think is right. I think maybe this makes the branch WIP.
[13:45] <brendand> jgdx, no - we'll do whatever takes the least amount of time - if you need to, discuss it with kenvandine
[13:45] <jgdx> brendand, new bug then :)
[13:46]  * mpt wonders why the latest devel image is reported as “Ubuntu 14.10 (r3)”
[13:46] <mpt> Latest proposed, I mean
[13:46] <jgdx> brendand, then we could have some text added to an empty "previous networks" as well, or change the behaviour of the "Previous networks" list item if there are none.
[13:47] <brendand> mpt, what's the channel?
[13:47] <brendand> mpt, ubuntu-touch/ubuntu-rtm/14.09?
[13:47] <jgdx> mpt, ^ what do you think. If there are no previous networks, should the list item that opens the "previous networks" page be insensitive? Or placeholder text?
[13:47] <jgdx> I can't seem to find that in the spec.
[13:47] <mpt> brendand, “Ubuntu Utopic Unicorn (development branch) - armhf (20140929-030205)”
[13:48] <ogra_> mpt, becaue it reads the value from files we can not change without breaking the whole infrastructure (and all packages)
[13:48] <mpt> jgdx, ohhh, you caught me not following my own spec checklist — always specify what happens when a collection has zero items :-)
[13:48] <brendand> mpt, system-image-cli -i
[13:49] <mpt> brendand, in the terminal on the phone?
[13:49] <brendand> mpt, yes
[13:50] <mpt> LOL, it’s bent like a CRT
[13:51] <mpt> Ah, I installed ubuntu-rtm/devel by mistake … I guess Mako isn’t an important target for RTM :-)
[13:51] <brendand> mpt, yeah - retro
[13:51] <ogra_> mpt, bug 1362496 ... there was also a more detailed explanation about lsb-release/os-release changes by cjwatson that sadly isnt in a public ML
[13:51] <brendand> mpt, no i think that might be the right alias
[13:51] <jgdx> mpt, do I win anything?
[13:52] <brendand> mpt, yes that is the 'promoted' image
[13:52] <brendand> mpt, it's the most well tested image for RTM
[13:53] <brendand> mpt, which is not to say it's the one that works best :P
[13:53] <ogra_> it definitely lacks fixes the newer image have :)
[13:53] <ogra_> *images
[14:14] <brendand> mpt, everything ok then or were you looking for a different channel?
[14:16] <mpt> jgdx, you win a free spec update. <https://wiki.ubuntu.com/Networking?action=diff&rev2=246&rev1=245>
[14:16] <mpt> brendand, yeah, I’m just bothered that when I report bugs I include the image version number but it seems … non-unique
[14:17] <brendand> mpt, it's not unique by itself
[14:17] <brendand> mpt, you need to include the device and channel too
[14:18] <brendand> mpt, you can use ubuntu-bug on RTM if you specify APPORT_DISABLE_DISTRO_CHECK=1
[14:18] <jgdx> mpt, yay
[14:23] <popey> ted: your app startup app seems broken. on my device it's not showing any app starts newer than 4th sept
[14:27] <ted> popey, Hmm, we should ping QA to see if they're still generating the results.
[15:11] <jgdx> hey brendand, that prev network branch went through?
[15:13] <cyphermox_> mzanetti: are you the right person to deal with qtubuntu, re bug 1357321
[15:14] <cyphermox_> ie. making use of connectivity-api whether it's possible, instead of QNetworkAccessManager?
[15:14] <cyphermox_> lpotter: hey
[15:15] <mzanetti> cyphermox: he started today with us and timezone is Australia... but yeah, I think he's gonna pick this one up
[15:16] <cyphermox> mzanetti: ah, that's why I didn't recognize the name ;)
[15:16] <brendand> jgdx, not yet. going to do it now
[15:16] <kenvandine> brendand, thanks!
[15:16] <jgdx> brendand, thank you
[15:16] <cyphermox> mzanetti: still, what are your thoughts on porting things to use connectivity-api instead?
[15:16] <mzanetti> cyphermox: define "things"
[15:16] <cyphermox> is it even possible considering the api requires indicator-network?
[15:16] <cyphermox> mzanetti: scopes, apps
[15:16] <mzanetti> -1
[15:17] <cyphermox> care to expand? :)
[15:17] <mzanetti> I don't like replacing existing upstream Qt api's with custom ones
[15:17] <cyphermox> or you know, maybe let's take this to the bug report directly instead, so tere's a clear trace of decisions
[15:18] <mzanetti> cyphermox: apps would need to #ifdef ubuntu everything related to network
[15:18] <cyphermox> mzanetti: I don't either, but this is special
[15:18] <cyphermox> are apps, being confined, even able to speak to NM via Qt to get the information?
[15:18] <cyphermox> ie. is it done centrally somehow, or per-app?
[15:18] <mzanetti> yeah, you should have only one QNetworkAccessManager per app
[15:19] <cyphermox> that's not what I meant
[15:19] <cyphermox> but if there's one per app; if apps can't access NM, it won't help them
[15:20] <cyphermox> the purpose of connectivity-api is to have one trusted way to get connectivity information for any apps or scopes or whatnot rather than digging into the NM api
[15:20] <brendand> jgdx, a bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1377991
[15:20] <brendand> jgdx, now i'll sign it off
[15:20] <jgdx> brendand, thanks!
[15:24] <mzanetti> cyphermox: what do you mean with digging into the NM api?
[15:25] <cyphermox> mzanetti: you need to get things from NM, via DBus, when you use QNetworkAccessManager to figure out whether you're connected and such
[15:26] <cyphermox> mzanetti: security concerns were that there are tons of things exposed in the NM DBus API; so it's not supposed to be included in what apps can use
[15:26] <cyphermox> mzanetti: however, connectivity-api is a "trusted helper", which does have the ability to speak to NM for you to get the information you need
[15:26] <mzanetti> cyphermox: hmm... I don't know how that stuff is implemented in the backend, but seems to me like connectivity-service should be used as between QtNetwork and actual NM
[15:27] <cyphermox> mzanetti: i have no idea how much this affects you
[15:27] <cyphermox> connectivity-service doesn't appear to use QtNetwork
[15:27] <cyphermox> (at least to my untrained eye)
[15:27] <mzanetti> no, the other way round
[15:27] <cyphermox> perhaps
[15:27] <mzanetti> but again, I don't know how pluggable QtNetwork backends are
[15:27] <cyphermox> but I haven't seen a connectivity-api bearer plugin
[15:28] <cyphermox> if we had that in the first place, there probably wouldn't be this conversation :)
[15:28] <mzanetti> heh, probably
[15:28] <cyphermox> hehe
[15:28] <mzanetti> well, lets see Lorn's verdict
[15:28] <cyphermox> anyway, all good if someone is looking into it, yes
[15:29] <cyphermox> fixing the bearer will bring good anyway
[15:34] <tsdgeos> renatu: https://code.launchpad.net/~aacid/dialer-app/addi18ntr not into a release yet?
[15:36] <renatu> tsdgeos, boiko and bfiller can help you with that
[15:37] <tsdgeos> bfiller: ↑↑
[15:37] <bfiller> tsdgeos: in a silo now
[15:38] <bfiller> silo 3 on rtm
[15:38] <tsdgeos> bfiller: cool :)
[15:40] <sil2100> bfiller: hey! Do you know from boiko if the ubuntu-rtm dialer-app failures got already fixed?
[15:42] <bfiller> sil2100: I don't think they have yet
[15:43] <bfiller> trying to reproduce them with our silo
[15:43] <bfiller> sil2100: does it occur on krillin or just mako?
[15:46] <sil2100> bfiller: those were reproducible on both mako and krillin IIRC
[15:46] <sil2100> bfiller: we know krillin for sure, let me check if mako still
[15:53] <jgdx> I'm an uncle, so later!
[16:07] <Isotop7> is there anything i need to activate besides the notification in the system settings and the permissions for each app to generate notifications? Apps like facebook and gmail dont generate messages...i use a make device with dualbooted ubuntu touch.
[16:40] <kenvandine> Wellark, how can i tell which context is the currently used one?
[16:41] <dobey> Isotop7: did you sign into those services under "Accounts" in system settings?
[16:41] <kenvandine> Wellark, i think it's failing to activate it, but no errors are thrown
[16:57] <Isotop7> dobey: i activated notifications in the notifications menu and gave all permissions in the account menu...
[16:58] <dobey> Isotop7: did you only log in to facebook through the app, or did you sign in in the accounts settings as well?
[17:00] <Isotop7> dobey: im logged in in the facebook app and i registered my account and gave the permission to notify me...i could try to delete the account and resign it on the ubuntu....
[17:01]  * dobey thinks there is a communication problem here
[17:03] <dobey> Isotop7: if you open System Settings, and then in there tap on 'Accounts', is Facebook listed in the accounts?
[17:03] <dobey> err
[17:04] <dobey> is "Facebook" listed as a logged in account; not in the list of new account types you can create, that is
[17:05] <Isotop7> dobey: i have a signed in account in the ubuntu account menu...
[17:05] <dobey> ok
[17:06] <dobey> Chipaca, ralsina_: ^^
[17:07] <ralsina_> Isotop7: inside the account in settings, you may see a " notifications" switch, you need to enable it
[17:08] <ralsina_> Isotop7: facebook doesn't work currently (needs special magic credentials)
[17:09] <Chipaca> was about to say, facebook still needs frobbing
[17:09] <Chipaca> i don't know the particular frobbage
[17:13] <Isotop7> ralsina_: i activated this also... why isnt it working? isnt it a problem that the developers just framing the webapps? wouldnt it be much better to build native apps? Are there any official apps which support notifications?
[17:14] <ralsina_> Isotop7: I know at least twitter works because I use it :-)
[17:14] <ralsina_> Isotop7: would I like to have native twitter apps? Sure. But we also want webapps to be integrated and support push notifications.
[17:15] <ralsina_> Isotop7: do you also have a u1 account created?
[17:15] <Isotop7> ralsina_: yes i have everything connected except flickr because i wanted to test the notifications :D
[17:16] <Wellark> kenvandine: yeah, debugging with awe and cyphermox
[17:16] <ralsina_> Isotop7: then I probably need the push client logs and the account-polld logs
[17:16] <Isotop7> ralsina: ok...i didnt know that there were webapps which support a kind of api to generate notifications on a mobile phone...
[17:17] <Isotop7> ralsina_: okay...do i get them via adb in the normal /var/log directory?
[17:17] <ralsina_> Isotop7: well, it's a bit more complicated than that, but yes, in the end that works :-)
[17:17] <ralsina_> Isotop7: there is a logviewer app in the store that makes it easy
[17:17] <ralsina_> http://victorpalau.net/2014/01/08/ubuntu-touch-logviewer/
[17:17] <Isotop7> ralsina_ : yeah im sorry for my lack of knowledge but i like to think positive :D
[17:18] <Isotop7> ralsina: oh thank you :)
[17:19] <ralsina_> Isotop7: I need to go get lunch, but please pastebin wherever and I'll take a look right away
[17:19] <Isotop7> oh thanks :)
[17:20] <Wellark> kenvandine: seems like NM or something is broken :(
[17:43] <n-iCe> did the ubuntu phone os got stable?
[17:44] <lotuspsychje> n-iCe: RTM is out and already nice and stable
[17:44] <nhaines> lotuspsychje: no it's not.
[17:44] <lotuspsychje> nhaines: cant it run on devices yet?
[17:45] <nhaines> lotuspsychje: there is no RTM release yet.
[17:45] <n-iCe> oh
[17:45] <n-iCe> so it is not stable?
[17:45] <n-iCe> I have a N5
[17:45] <lotuspsychje> wel developer version seems stable for my n7
[17:45] <nhaines> n-iCe: it's pretty stable if you stay on the promoted builds.  Either devel or ubuntu-rtm/14.09
[17:46] <n-iCe> do you guys use it a daily driver?
[17:46] <nhaines> I have an N5 too and except for lack of bluetooth support it's pretty nice.
[17:46] <nhaines> I don't use it as a daily driver because there's no bluetooth and Unity 8 keeps locking up, but the Unity issue has been fixed, I think.  I need Android-only apps still for the moment though.
[17:46] <popey> its my daily phone
[17:47] <n-iCe> I use bluetooth a lot
[17:47] <n-iCe> so no way I can use the ROM.
[17:47] <nhaines> lotuspsychje: "there's a developer version that works well" isn't the same as "it's been released to manufacturers and is production ready."
[17:47] <nhaines> n-iCe: with MultiROM Manager you can dualboot and test it out.  That's worth doing at least once.  :)
[17:47] <n-iCe> I have, months ago
[17:48] <nhaines> Design is very different now.
[17:48] <lotuspsychje> different how
[17:49] <n-iCe> is it?
[17:49] <nhaines> Multitasking is better, indicator menus don't lag...
[17:49] <n-iCe> is that design?
[17:50] <nhaines> The app switcher is design.
[17:50] <nhaines> Speaking of, scopes are very interesting now.
[17:51] <lotuspsychje> and handy ubuntu app store
[17:51] <n-iCe> oh is there an app store now?!
[17:51] <n-iCe> is whatsapp ready?
[17:51] <nhaines> It's a fullblown scope.
[17:51] <nhaines> Whatsapp will never be ready.
[17:52] <lotuspsychje> lol
[17:52] <Isotop7> epic fail :D
[17:52] <Isotop7> if you want to run whatsapp, youll never gonna use ubuntu touch
[17:52] <n-iCe> then it is not for me
[17:52] <n-iCe> can't live without it.
[17:52] <Isotop7> do think about apps like telegram or something like that :)
[17:52] <n-iCe> how can you :p ?
[17:52] <lotuspsychje> well at least ubuntu touch is safe to use
[17:53] <nhaines> n-iCe: I've never used it nor do I care to.  Easy.  :P
[17:53] <Isotop7> you have to keep in mind on what ubuntu touch is aiming on...
[17:53] <n-iCe> nhaines: I bet is because of your country
[17:53] <n-iCe> Isotop7: what is that
[17:54] <nhaines> Once Ubuntu gets big, Whatsapp may follow.  But they shutdown the community port.
[17:54] <Isotop7> n-iCe: https://telegram.org/
[17:55] <n-iCe> Isotop7: people here does not use that
[17:55] <Isotop7> i dont think it will ever be featured...they pursue people who try to build apis...they dont like open stuff....
[17:55] <Isotop7> where do you come from? :D
[17:55] <n-iCe> México, 99% of Mexicans use whatsapp.
[17:56] <Isotop7> maybe these are just your personal pfer
[17:56] <Isotop7> *preferences :D
[17:56] <n-iCe> mobile phone providers give whatsapp for free
[17:56]  * mhall119 finds the 99% figure dubious
[17:56] <lotuspsychje> lol
[17:56] <Isotop7> okay...i dont know much about mexico but this is very sad....
[17:56] <Isotop7> in germany people use clients like whistle.im, telegram, threema or minor clients...
[17:56]  * lotuspsychje thinks many users are addicted to their smartphones too much...
[17:57] <Tassadar> that would mean 99% have smartphone
[17:57]  * popey prints out and frames "18:51:57 < nhaines> Whatsapp will never be ready."
[17:57] <n-iCe> 99% using smartphones of course...
[17:57] <popey> [CITATION NEEDED]
[17:57] <Tassadar> [ACTUAL SIZE]
[17:57] <mhall119> as nhaines said though, only WhatsApp (now Facebook) can bring WhatsApp support to Ubuntu, or any other platform, and they've so far been very restrictive about what they allow
[17:58] <lotuspsychje> Tassadar: even if people are poor, they got smartphone anways :p
[17:58] <mhall119> even Android tablets and iPad don't have WhatsApp clients
[17:58] <Tassadar> why do you even need whatsapp, to me it looks like just another proprietary IM thingy
[17:59] <n-iCe> the thing is
[17:59] <n-iCe> I need it :)
[17:59] <mhall119> Tassadar: same reason people need Facebook, because that's what everybody they want to talk to is using
[17:59] <n-iCe> ubuntu phone is just not for me :p, thank you guys for all the info!
[17:59] <mhall119> n-iCe: sorry to hear that, but do keep an eye on it because someday it might be
[17:59] <lotuspsychje> lol
[17:59] <Tassadar> another ICQ then
[17:59] <mhall119> Tassadar: basically, yeah
[17:59] <popey> 11317622
[17:59]  * mhall119 never actually used ICQ
[18:00] <lotuspsychje> soon it might be the most popular mobile Os
[18:00]  * Tassadar looks at jabber and cries
[18:00] <popey> I used it in 1996
[18:00] <ogra_> Tassadar, depends which country you are in ... whatsapp is the #1 messaging service in germany ... beating even SMS by factor three
[18:00] <nhaines> I last used it in 1998.
[18:00] <dobey> ICQ is a mobile OS?
[18:00] <ogra_> (i dont use it either and i'm german ... but i read the stats)
[18:00] <Isotop7> I think tassadar is right...everybody thinks he needs to use it because everybody thinks he needs to use it :D
[18:00] <nhaines> dobey: first mass-adopted instant messaging software.
[18:00] <lotuspsychje> dobey: lol i was talking about ubuntu touch :p
[18:01] <dobey> nhaines: i know what icq is
[18:01] <mhall119> Isotop7: there's some truth to that, the main benefit of messaging services isn't their actual capability, it's who you can talk to with them
[18:01] <nhaines> Tassadar: do you work on the N5 community port or just run the build services?
[18:01]  * mzanetti can't believe he still remembers his ICQ number from 2002
[18:01] <dobey> 2002?
[18:02] <dobey> noob.
[18:02]  * mhall119 can't believe mzanetti started using ICQ in 2002
[18:02] <ogra_> Isotop7, well, you use what your friends use
[18:02] <mzanetti> haha :D
[18:02] <Tassadar> mostly just run the server (I don't have to do anything to it, it is automated), sometimes I poke at it a little bit (like I fixed the backlight issue a while ago)
[18:02] <ogra_> Isotop7, its a peer pressure thing
[18:02] <mzanetti> well, can't remember when it actually was
[18:02] <mzanetti> but yeah... at earliest 200 I think...
[18:02] <Tassadar> 416623426 lol, I remember it too :D
[18:02] <nhaines> Mine was 217XXXX but I don't remember it anymore.  I could probably figure it out  :)
[18:02] <mzanetti> 2000
[18:03] <nhaines> I vaguely miss using Trillian.  Empathey and Pidgin are great but I miss the emoticons.  :P
[18:03]  * mhall119 remembers Trillian
[18:03]  * popey hugs bitlbee
[18:03] <mzanetti> +1
[18:03] <nhaines> Tassadar: ah, I was wondering if there was anything I could do to kick the bluetooth stack on N5.
[18:03] <Tassadar> you could fix it :x
[18:03] <mhall119> I used Trillian up until I discovered Gaim (now Pidgin)
 !info bitlbee
 bitlbee (source: bitlbee): An IRC to other chat networks gateway (default version). In component universe, is optional. Version 3.2.1+otr4-1 (trusty), package size 196 kB, installed size 665 kB
[18:03] <Isotop7> meine meinung, ogra_
[18:03] <dobey> i miss all the random "help me learn english please" requests on icq from chinese/russian girls
[18:04] <dobey> yeah nhaines, fix it
[18:04] <Isotop7> yeah...these times were marvelous :D
[18:05] <lotuspsychje> and then all the underground icq hacking toolz
[18:05] <nhaines> I don't know how to fix it.  But sometimes I'm annoyed enough to want to try anyway.
[18:05] <Isotop7> billions and billions of aftermarket emojis....
[18:05] <dobey> +++ath
[18:05] <dobey> best hacking tool evar
[18:06] <nhaines> Ha, those were the days.
[18:06] <dobey> emoticons
[18:06] <dobey> not emojis
[18:06] <Tassadar> nhaines: I dunno either, I'd have to do research too
[18:06] <nhaines> Is bluetooth at least working and stable on N4?
[18:06] <lotuspsychje> and now the whole world is vunerable
[18:06] <Isotop7> im so sorry, dobey :D
[18:06] <dobey> and if you insist on being a faux japanophile, emoji
[18:07] <Isotop7> it is nhaines!
[18:07] <Tassadar> might be something stupid like missing config option or something entirely differnt
[18:07] <dobey> nhaines: afaik yes, but i can't stand looking at the n4; i only use it to test things :)
[18:07] <nhaines> Isotop7: good, because that's the requisite to me wasting time trying to fix the N5.  :P
[18:08] <nhaines> dobey: N4 screens are potatoes next to the N5.  :)
[18:08] <dobey> Tassadar: or probably some crazy driver thing
[18:08] <dobey> nhaines: it's not just the screen. the phone itself just looks so fragile and too glossy
[18:09] <Isotop7> dont talk about n4s...the back of mine broke saturday night...it looks awful....but i dont know how to port it to my samsung galaxy s4...so i have to use this little shitty brick with this damn nice ubuntu :)
[18:10] <ogra_> it is october already ... before end of the year you will be able to buy an ubuntu phone ;)
[18:10] <nhaines> ogra_: If they have working bluetooth I'll consider it.  ;)
[18:11] <lotuspsychje> ogra_: sounds promising
[18:11] <ogra_> indeed they will :)
[18:11]  * popey plays music on a bluetooth speaker from his ubuntu phone
[18:11] <dobey> nhaines: are you in the US?
[18:11] <ogra_> popey, ssshhh
[18:11] <ogra_> !
[18:11] <nhaines> Actually, I'm torn.  Obviously I want to support Ubuntu and help sales.  On the other hand, I want a convergence-ready device without buying another phone in two more years.  :P
[18:11] <nhaines> dobey: I am.
[18:11]  * lotuspsychje plays video's from popey's youtube app
[18:11] <popey> "app"
[18:11] <mhall119> "popey's"
[18:11] <rickspencer3> is this the right place to log bugs for the sound indicator on the phone?
[18:11] <rickspencer3> https://bugs.launchpad.net/ubuntu/+source/indicator-sound/
[18:12] <ogra_> rickspencer3, yes
[18:12] <dobey> nhaines: just fix bt on n5 :)
[18:12] <vitimiti> Hi
[18:13] <nhaines> dobey: I'll trade Canonical a fix for BT on N5 if they send me a krillin device for differential troubleshooting.  ;)
[18:13] <Isotop7> so ubuntu touch is rather focused to release customized build to new devices then porting it down to the most recent devices?
[18:13] <nhaines> Isotop7: Ubuntu's focused on getting the OS and SDK and APIs right.
[18:13] <ogra_> Isotop7, it is focused on getting the first stable release out
[18:13] <nhaines> Porting to any device is the manufacturer's job.
[18:13] <ogra_> Isotop7, once where is an actual stable base porting will be a lot easier to handle
[18:14] <Isotop7> okay...seems about right...
[18:14] <Tassadar> and an updated guide)
[18:14] <ogra_> the current prob with ports is that most of them were against quantal and never updated ...
[18:14] <ogra_> once we have a stable base updating the docs, providing some scripts etc will be easy
[18:15] <Isotop7> "was der bauer nicht kennt, frisst er nicht!"
  I miss my T-Mobile G1.  :)
[18:30] <dobey> this is how i feel about things like "lolspeak" https://www.youtube.com/watch?v=8HicYNBTpK0
[19:14] <dobey> how does one get the infographics stuff working again? my phone has said "No data sources available" for many weeks now (or months maybe)
[19:23] <ahayzen> dobey, possibly this bug 1372502
[19:24] <ahayzen> dobey, which was from this bug 1359022
[19:31] <dobey> why is that not even tagged for rtm, and still set to undecided importance? :-/
[19:31] <ahayzen> dobey, there is another one for rtm i think...
[19:31] <dobey> how many bugs do we need for the same problem?
[19:32] <ahayzen> dobey, or maybe not
[19:32] <ahayzen> dobey, somewhere between those two bugs lol
[19:32] <ahayzen> dobey, ah i was thinking of this one bug 1374553
[19:40] <dobey> huh
[19:40] <dobey> that bug is a lie
[19:40] <dobey> it's not fixed
[19:42] <ahayzen> dobey, i think it basically broke again? or something like that lol
[19:47] <dobey> i see what the problem is
[19:47] <dobey> my nexus4 seems to have the correct permissions
[19:48] <dobey> so it was "fixed" for completely new installs
[19:48] <dobey> but if you've already got an install that was broken by a previous update, the new updates don't fix the permissions on the directory
[19:48] <dobey> ogra_, jdstrand: ^^ can we do something about that?
[19:50] <jdstrand> the only way to do it in an upgrade is via some upstart job since postinst scripts aren't run
[19:51] <jdstrand> perhaps there is already a job for things like that
[19:51]  * jdstrand doesn't know
[20:00] <ogra_> dobey, the vanishing infographics had nothing to do with permissions, the dir where it stores data was non existent for a few images ... nothing about permissions changed there (there was simply no homedir defined for the usermetrics user)
[20:00] <ogra_> it was gone for about 5 images and re-added ...
[20:01] <dobey> ogra_: that isn't true
[20:01] <ogra_> ??
[20:01] <ogra_> how do you mean ?
[20:01] <ogra_> it is definitely true for 6 devices here
[20:01] <dobey> ogra_: the broken images didn't remove it during OTA updates
[20:02] <ogra_> they did
[20:02] <ogra_> the mountpoint was gone
[20:02] <ogra_> so the bind mount for the writable dir couldnt happen
[20:02] <dobey> ogra_: then how do i have a current image with a directory with the wrong permissions?
[20:02] <ogra_> after the mountpoint was re-added all devices here have infographics again
[20:02] <ogra_> no idea
[20:02] <ogra_> definitely not because of this specific issues
[20:03] <ogra_> *issue
[20:03] <ogra_> the most recent issue simply didnt have the mountpoint in the readonly image
[20:03]  * dobey wish there was an infographics app to browse the data in the db
[20:04]  * ogra_ vanishes back into the night
[20:04] <dobey> well, i didn't need to remount with rw to be able to chown, either
[20:31] <tset> hi
[20:32] <tset> I've just installed using this command: ubuntu-device-flash --channel=ubuntu-touch/ubuntu-rtm/14.09-proposed --bootstrap
[20:32] <tset> now I'm stuck at google
[20:32] <tset> my device is nexus 4
[20:33] <dobey> stuck for how long?
[20:33] <tset> very long
[20:33] <tset> 10 miutes
[20:34] <dobey> try rebooting?
[20:34] <tset> done that
[20:38] <tset> any idea?
[20:38] <dobey> reboot to bootloader and try again?
[20:39] <tset> dobey: done that 3 times now
[20:39] <tset> even tryed different versions
[20:39] <dobey> tset: is this a new device?
[20:39] <tset> no
[20:40] <tset> my old phone. run perfectly with cm11
[20:40] <dobey> flash the latest android onto it, let it boot up to the android start screen, then reboot to bootloader and try again
[20:41] <tset> okej, I'll try that. thanks
[21:00] <tset> dobey: it worked! love you man :)
[23:50] <^Manu> Hi people. I just trying out Ubuntu touch on my SGS3. It
[23:51] <^Manu> it's basically unusable, but it also says the binary is from mid last year.
[23:51] <^Manu> wondering if anyone has any experience with this device, and if there are binaries that aren't over a year old...


[22:46] <Takyoji_> Anyone have trouble with the Facebook plugin in Pidgin?
[23:24] <Takyoji_> I'm so glad; I just had the most beautiful Ubuntu installation for a friend.
[23:24] <Takyoji_> Wireless worked out of the box and everything perfectly.
[23:24] <Takyoji_> The only issue was that at first boot, the mouse/keyboard didn't work.
[23:25] <Takyoji_> And in other news, something terrible that seems to have happened recently: http://helpshawnpowersfamily.chipin.com/help-shawn-powers-family
[23:25] <Takyoji_> Shawn Powers' house supposedly burned down
[23:27] <Takyoji_> Well, not entirely burned down I suppose: http://www.natuba.com/photo/JWckHL/
[23:27] <Takyoji_> http://twitter.com/shawnp0wers


 I saw that
 the Nexus 9 got 7.1.1 already
 @ahoneybun, So.. get her a Mi Box of her own, she can take advantage of the trial and get a Mii box
 she has no use for it
 I don't think so anyway
 @AdamOutler
 Yoooo
 11


[12:16] <stickupkid> manadart, download integration tests https://github.com/juju/juju/pull/12270
[12:16] <manadart> stickupkid: Yep will look; just putting up the Origin one now.
[12:16] <stickupkid> nice
[12:35] <manadart> stickupkid: https://github.com/juju/juju/pull/12446
[13:05] <stickupkid> manadart, code is fine, just doing q&a when I get back from lunch
[16:37] <stickupkid> manadart, or achilleasa https://github.com/juju/juju/pull/12448 architecture in acceptance tests
[16:37] <manadart> stickupkid: I have to make a move here. Kids to fetch.
[16:38] <stickupkid> monday is fine, was just a ping ;-)
[16:38] <stickupkid> no rush
[16:38] <manadart> Done deal.


[00:35] -queuebot:#ubuntu-ci-eng- xnox, https://bileto.ubuntu.com/#/ticket/3214 Dependency wait (bionic/juju-mongodb3.4). Diff missing (bionic/juju-mongo-tools3.4, bionic/juju-mongo-tools3.6). Failed to build (bionic/juju-mongodb3.6)


[00:21] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[00:48] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Currently building (xenial/ubuntu-keyboard, zesty/ubuntu-keyboard). Failed to build (xenial/unity8). Needs rebuild due to burned version number (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir-gles). Needs rebuild due to new commits (zesty/qtmir, zesty/qtubuntu, zesty/ubuntu-system-settings, zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ub
[00:53] -queuebot:#ubuntu-ci-eng- artmello, https://bileto.ubuntu.com/#/ticket/2482 Preparing packages
[01:09] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (xenial/unity8). Needs rebuild due to burned version number (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir-gles). Needs rebuild due to new commits (zesty/qtmir, zesty/qtubuntu, zesty/ubuntu-system-settings, zesty/unity8). Pending binary packages (xenial/ubuntu-keyboard, zesty/ubuntu-keyboard). Successfully built (xenial/indicator-keyboard, xenial/qtubuntu, xenial/qtubuntu-gles, xeni
[01:24] -queuebot:#ubuntu-ci-eng- artmello, https://bileto.ubuntu.com/#/ticket/2482 Pending binary packages
[01:28] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (xenial/unity8). Needs rebuild due to burned version number (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir-gles). Needs rebuild due to new commits (zesty/qtmir, zesty/qtubuntu, zesty/ubuntu-system-settings, zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-se
[01:36] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[01:57] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://bileto.ubuntu.com/#/ticket/2311 Preparing packages
[02:04] -queuebot:#ubuntu-ci-eng- artmello, https://bileto.ubuntu.com/#/ticket/2482 Successfully built
[02:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (xenial/unity8). Needs rebuild due to burned version number (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir-gles). Needs rebuild due to new commits (zesty/qtmir, zesty/ubuntu-system-settings, zesty/unity8). Pending binary packages (xenial/qtubuntu, xenial/qtubuntu-gles, zesty/qtubuntu, zesty/qtubuntu-gles). Successfully built (xenial/indicator-keyboard, xenial/ubuntu-keyboard, xenial
[02:21] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://bileto.ubuntu.com/#/ticket/2311 Failed to build (xenial/address-book-app, xenial/telepathy-qt, zesty/telepathy-qt). Needs rebuild due to new commits (zesty/address-book-app, zesty/messaging-app). Pending binary packages (xenial/messaging-framework, zesty/messaging-framework). Successfully built (xenial/address-book-service, xenial/libircclient, xenial/messaging-app, xenial/mfw-plugin-irc, zesty/address-book-servic
[02:27] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (xenial/unity8). Needs rebuild due to burned version number (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir-gles). Needs rebuild due to new commits (zesty/qtmir, zesty/ubuntu-system-settings, zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, zesty/ind
[02:31] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[02:42] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://bileto.ubuntu.com/#/ticket/2311 Failed to build (xenial/address-book-app, xenial/telepathy-qt, zesty/telepathy-qt). Needs rebuild due to new commits (zesty/address-book-app, zesty/messaging-app). Successfully built (xenial/address-book-service, xenial/libircclient, xenial/messaging-app, xenial/messaging-framework, xenial/mfw-plugin-irc, zesty/address-book-service, zesty/libircclient, zesty/messaging-framework, zes
[02:48] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Currently building (xenial/qtmir, xenial/qtmir-gles, zesty/qtmir, zesty/qtmir-gles). Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/ubuntu-system-settings, zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, zesty/indicator-keyboard, zesty/q
[03:09] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/ubuntu-system-settings, zesty/unity8). Pending binary packages (xenial/qtmir, zesty/qtmir-gles). Successfully built (xenial/indicator-keyboard, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, zesty/indicator-keyboard, zesty/qtmir, ze
[03:28] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/ubuntu-system-settings, zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, zesty/indicator-keyboard, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubun
[04:14] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[04:22] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 /: Failed to upload diffs. Please try regenerating diffs
[04:36] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[05:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Currently building (xenial/ubuntu-system-settings, zesty/ubuntu-system-settings). Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-touch-session, zesty/indicator-keyboard, zesty/qtmir, zesty/qtmir-gles, zesty/q
[05:28] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Currently building (xenial/ubuntu-system-settings). Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/unity8). Pending binary packages (zesty/ubuntu-system-settings). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-touch-session, zesty/indicator-keyboard, zesty/qtmir,
[05:48] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/unity8). Pending binary packages (xenial/ubuntu-system-settings). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-touch-session, zesty/indicator-keyboard, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubuntu-g
[06:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (xenial/unity8). Needs rebuild due to new commits (zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, zesty/indicator-keyboard, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/ubuntu-keyboard
[07:48] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[08:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Currently building (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/unity8, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/ubuntu-keyboard, zesty/ubuntu-system-settings, zesty/unity8). Failed to build (zesty/indicator-keyboard). Successfully built (xenial/ubun
[08:28] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Currently building (xenial/ubuntu-system-settings, xenial/unity8, zesty/ubuntu-system-settings, zesty/unity8). Failed to build (zesty/indicator-keyboard). Pending binary packages (xenial/qtmir, xenial/ubuntu-keyboard, zesty/ubuntu-keyboard). Successfully built (xenial/indicator-keyboard, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-touch-session, zesty/qtmir, zesty/qtmir
[08:46] <Saviq> trainguards, can someone please retry https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2481/+build/12052165 - looks like a flaky test, thanks!
[08:49] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (zesty/indicator-keyboard). Pending binary packages (xenial/ubuntu-system-settings). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-touch-session, xenial/unity8, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/ubuntu-keyboard, zesty/ubuntu-system-s
[09:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Failed to build (zesty/indicator-keyboard). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, xenial/unity8, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/ubuntu-keyboard, zesty/ubuntu-system-settings, zesty/ubuntu-touc
[09:42] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2506 Publishing packages
[09:42] <morphis> vigo: ping
[09:43] <vigo> morphis, pong
[09:43] <morphis> vigo: where are you with testing the wifi-ap snap leaving problems on the db aside?
[09:44] <vigo> morphis, I gave it another try, but is definetly not working for me on db even with with the adapter
[09:45] <Mirv> Saviq: retrying
[09:45] <vigo> with wifi off there is no way I can get wifi.status true
[09:45] <morphis> vigo: did you test it on the pi3?
[09:47] <vigo> morphis, yes, and vrruiz double checked it for me as I had also some problems
[09:47] <vigo> It worked reliably for him
[09:52] <morphis> vigo: so for pi3 everything is fine?
[09:56] <vigo> morphis, sure!
[09:57] <morphis> vigo: then lets approve and we will see that we get things fixed on the db
[09:58] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2373 Failed to build (xenial/unity8). Needs rebuild due to higher version at destination (xenial/unity-api, zesty/unity-api). Needs rebuild due to new commits (zesty/miral, zesty/qtmir, zesty/unity8). Successfully built (xenial/miral, xenial/qtmir, xenial/qtmir-gles, zesty/qtmir-gles)
[09:59] <vigo> morphis, wow I should have approved it, so sorry I moved the card in trello to passed but forgot to approve
[10:00] -queuebot:#ubuntu-ci-eng- morphis, https://bileto.ubuntu.com/#/ticket/2444 QA Signoff: Approved
[10:00] -queuebot:#ubuntu-ci-eng- dandrader, https://bileto.ubuntu.com/#/ticket/2457 Needs rebuild due to burned version number (xenial/unity-api, zesty/unity-api). Needs rebuild due to new commits (zesty/qtmir, zesty/unity8). Successfully built (xenial/qtmir, xenial/qtmir-gles, xenial/unity8, zesty/qtmir-gles)
[10:03] <morphis> vigo: ah :-)
[10:03] <morphis> thanks
[10:08] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2506 Proposed pocket (zesty/unity-api). Release pocket (xenial/unity-api)
[10:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Successfully built
[10:54] <oSoMoN> rvr, everything alright with silo 2510 ?
[10:55] <rvr> oSoMoN: I am checking right now
[11:06] <oSoMoN> cheers
[11:27] <vigo_> abeato, ping
[11:27] <abeato> vigo_, pong
[11:27] <vigo_> should this silo work on unity8-deb?
[11:28] <abeato> vigo_, I have notr tried that, could be the case
[11:28] <vigo_> abeato, I just tried
[11:28] <abeato> vigo_, I tested with the unity8 snap, on xenial+proposed
[11:29] <abeato> vigo_, no luck
[11:29] <abeato> ?
[11:29] <vigo_> abeato, currently mediaplayer window appears but it comes with an error, it says
[11:30] <vigo_> No video selected to play. connect your phone to your computer etc
[11:30] <vigo_> I'm on xenial+overlay and all the things from the doc installed
[11:31] <abeato> vigo_, are you using the deb mediaplayer?
[11:33] <vigo_> abeato, yes, I am, mediaplayer-app
[11:34] <abeato> vigo_, ok, could you pastebin mediaplayer/media-hub traces?
[11:35] <vigo_> abeato, ok I'll grab some
[11:36] <abeato> thanks
[11:44] <vigo_> abeato, where can I find them?
[11:45] <abeato> vigo_, aren't you launching them from the command line?
[11:46] <vigo_> abeato, yes, you meant just the output from cli?
[11:46] <abeato> vigo_,  yep
[11:48] -queuebot:#ubuntu-ci-eng- pete-woods, https://bileto.ubuntu.com/#/ticket/2506 Release pocket
[11:49] <vigo_> abeato, https://pastebin.canonical.com/180634/
[11:50] <abeato> vigo_, and medi-hub output?
[11:54] <vigo_> abeato, https://pastebin.canonical.com/180635/
[11:55] <abeato> vigo_, mind checking output of "dpkg -l | grep plugins-bad
[11:55] <abeato> "? :)
[11:57] <vigo_> abeato, https://pastebin.canonical.com/180636/
[11:58] <abeato> vigo_, not the right version: check https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2472/+packages
[11:58] <abeato> vigo_ should be 1.8.3-1ubuntu0.3~overlay2
[11:58] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2373 Failed to build (xenial/unity8). Needs rebuild due to higher version at destination (xenial/unity-api). Needs rebuild due to new commits (zesty/miral, zesty/qtmir, zesty/unity-api, zesty/unity8). Successfully built (xenial/miral, xenial/qtmir, xenial/qtmir-gles, zesty/qtmir-gles)
[11:59] <vigo_> abeato, ack I'll get back to you in a bit
[11:59] <abeato> cool, thanks
[12:00] -queuebot:#ubuntu-ci-eng- dandrader, https://bileto.ubuntu.com/#/ticket/2457 Needs rebuild due to burned version number (xenial/unity-api). Needs rebuild due to new commits (zesty/qtmir, zesty/unity-api, zesty/unity8). Successfully built (xenial/qtmir, xenial/qtmir-gles, xenial/unity8, zesty/qtmir-gles)
[12:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Needs rebuild due to new commits (zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, xenial/unity8, zesty/indicator-keyboard, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/ubuntu-keyboard, zesty/ubuntu-sys
[12:19] <vigo_> abeato, https://pastebin.canonical.com/180637/
[12:19] <vigo_> still fails with 1.8.3 overlay2
[12:20] <vigo_> same message and those are the outputs
[12:20] <abeato> vigo_, better output nonetheless
[12:20] <abeato> vigo_, what do you see on the screen?
[12:21] <vigo_> abeato, well the message is the same in mediaplayer window
[12:22] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[12:22] <vigo_> abeato, here it is https://trello.com/c/IcZoDBGA/4003-2472-2472-lxc-android-config-media-hub-qtvideo-node-qtubuntu-media-abeato
[12:23] <vigo_> abeato, at least with the right packages it can load mirclient and the backend
[12:23] <vigo_> what's the next step? :)
[12:23] <abeato> vigo_, this is weird: File not found: QUrl("file:///home/silotesting/--desktop_file_hint=unity8") false false
[12:24] <abeato> it should not interpret that as a file
[12:24] <abeato> vigo_ remove --desktop_file_hint=unity8 and see what happens
[12:31] <abeato> vigo_ pasting that makes the command fail for me too... it is one of those silly things when copying things from google docs...
[12:33] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 /: Failed to upload diffs. Please try regenerating diffs
[12:34] <abeato> vigo_ try to type yourself the --desktop option, looks like being a bad ascii code
[12:35] <vigo_> abeato, ok working now
[12:35] <abeato> \o/
[12:35] <vigo_> I just changed the position of --desktop to the end of the line
[12:35] <vigo_> :O
[12:36] <vigo_> now I can watch and hear it correctly
[12:36] <vigo_> :)
[12:36] <abeato> nice :)
[12:36] <abeato> vigo_, note that this is kind of experimental, so do not expect things to be perfect
[12:37] <abeato> vigo_ the idea is to land this and go on with incremental improvements
[12:37] <vigo_> abeato, I know, that's the beauty of this :P
[12:37] <vigo_> abeato, sounds good
[12:37] <abeato> lol
[12:37] <vigo_> I'm approving it :)
[12:38] <abeato> vigo_ nice, thanks :)
[12:45] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2472 QA Signoff: Approved
[12:46] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[12:46] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2472 Publishing packages
[12:48] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2472 Publish failed: Packaging diff requires ACK (xenial/media-hub, zesty/media-hub). alfonsosanchezbeato not authorized to upload gst-plugins-bad1.0 (xenial/gst-plugins-bad1.0, zesty/gst-plugins-bad1.0)
[12:49] <abeato> trainguards, please help with publishing https://bileto.ubuntu.com/#/ticket/2472
[12:49] <abeato> Laney, the zenial plugins-bad change is there too ^^
[12:49] <Laney> right
[12:50] <Laney> well it's not reviewed yet ...
[12:51] <abeato> Laney, ok, please take a look. Anyway we might delay the gstreamer zesty landing (maybe do it from another silo) and land the rest of the stuff
[12:51] <Laney> I will look, just busy with some other things first
[12:52] <abeato> sure, np
[12:52] <abeato> *nw
[12:53] <Laney> abeato: looks like you got some nice review too
[12:53] <abeato> Laney, yes, was good feedback, working on improve the plugin atm
[12:53] <Laney> :)
[13:15] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2472 Successfully built
[13:18] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Dependency wait (zesty/qtubuntu-print). Failed to build (xenial/ubuntu-printing-app, xenial/ubuntu-ui-extras, zesty/ubuntu-printing-app). Needs rebuild due to new commits (zesty/ubuntu-ui-extras). Successfully built (xenial/content-hub, xenial/qtubuntu-print, zesty/content-hub)
[13:21] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Preparing packages
[13:23] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2381 Failed to build (xenial/ubuntu-ui-extras). Needs rebuild due to new commits (zesty/ubuntu-system-settings, zesty/ubuntu-ui-extras). Successfully built (xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, zesty/ubuntu-settings-components)
[13:28] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2381 Preparing packages
[13:28] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Pending binary packages (zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, zesty/indicator-keyboard, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/ubuntu-keyboard, zesty/ubuntu-system-settings, zesty/ubun
[13:38] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Dependency wait (zesty/qtubuntu-print). Failed to build (xenial/ubuntu-printing-app, xenial/ubuntu-ui-extras, zesty/ubuntu-printing-app, zesty/ubuntu-ui-extras). Successfully built (xenial/content-hub, xenial/qtubuntu-print, zesty/content-hub)
[13:41] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2381 Too many merge targets: lp:ubuntu-ui-extras, lp:~phablet-team/ubuntu-ui-extras/printer-components
[13:42] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2472 Generating diffs
[13:45] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2472 Successfully built
[13:48] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Needs rebuild due to new commits (zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, xenial/unity8, zesty/indicator-keyboard, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/ubuntu-keyboard, zesty/ubuntu-sys
[13:51] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2264 Preparing packages
[13:53] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2514 Preparing packages
[13:57] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2381 Preparing packages
[13:58] -queuebot:#ubuntu-ci-eng- boiko tiagosh renato, https://bileto.ubuntu.com/#/ticket/2451 Preparing packages
[14:05] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://bileto.ubuntu.com/#/ticket/2311 Preparing packages
[14:06] -queuebot:#ubuntu-ci-eng- ChrisTownsend, https://bileto.ubuntu.com/#/ticket/2264 Failed to build (xenial/ubuntu-app-launch, zesty/ubuntu-app-launch). Successfully built (xenial/libertine, zesty/libertine)
[14:08] -queuebot:#ubuntu-ci-eng- boiko tiagosh renato, https://bileto.ubuntu.com/#/ticket/2451 vivid/ubuntu-system-settings: Failed to download DSC file https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+files/ubuntu-system-settings_0.4+15.04.20161129-0ubuntu1.dsc
[14:15] <abeato> Mirv, hi, I've seen you have regenerated the diffs in https://bileto.ubuntu.com/#/ticket/2472 , do you need something from my side to get this published?
[14:18] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2514 Failed to build (xenial/unity8, zesty/unity8). Pending binary packages (zesty/unity-api). Successfully built (xenial/unity-api)
[14:19] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[14:21] -queuebot:#ubuntu-ci-eng- boiko tiagosh renato, https://bileto.ubuntu.com/#/ticket/2451 Needs rebuild due to new commits (vivid/address-book-app, vivid/history-service, vivid/messaging-framework, vivid/telephony-service, vivid/ubuntu-system-settings). Successfully built (vivid/dialer-app, vivid/messaging-app, vivid/mfw-plugin-irc, vivid/telepathy-ofono)
[14:23] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2381 Failed to build (xenial/ubuntu-ui-extras, zesty/ubuntu-ui-extras). Successfully built (xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, zesty/ubuntu-settings-components, zesty/ubuntu-system-settings)
[14:36] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2514 Failed to build (xenial/unity8, zesty/unity8). Successfully built (xenial/unity-api, zesty/unity-api)
[14:40] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2514 Preparing packages
[14:41] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://bileto.ubuntu.com/#/ticket/2311 Failed to build (xenial/telepathy-qt, zesty/telepathy-qt). Needs rebuild due to new commits (zesty/messaging-app). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/libircclient, xenial/messaging-app, xenial/messaging-framework, xenial/mfw-plugin-irc, zesty/address-book-app, zesty/address-book-service, zesty/libircclient, zesty/messaging-framework, zes
[14:47] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Chroot problem (zesty/ubuntu-keyboard). Currently building (xenial/qtmir, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/unity8, zesty/qtmir, zesty/ubuntu-system-settings, zesty/unity8). Failed to build (zesty/indicator-keyboard). Pending binary packages (xenial/qtmir-gles, xenial/qtubuntu, zesty/qtmir-gles, zesty/qtubuntu). Successfully built (xenial/indicator-keyboard, xenial/qtub
[14:55] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2472 Publishing packages
[14:55] -queuebot:#ubuntu-ci-eng- oSoMoN ahayzen, https://bileto.ubuntu.com/#/ticket/2510 QA Signoff: Approved
[14:57] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2472 Publish failed: Packaging diff requires ACK (xenial/media-hub, zesty/media-hub). alfonsosanchezbeato not authorized to upload gst-plugins-bad1.0 (xenial/gst-plugins-bad1.0, zesty/gst-plugins-bad1.0)
[15:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Chroot problem (zesty/ubuntu-keyboard). Currently building (xenial/ubuntu-system-settings, zesty/ubuntu-system-settings, zesty/unity8). Failed to build (zesty/indicator-keyboard). Pending binary packages (xenial/ubuntu-keyboard). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-touch-session, zesty/qtmir, zesty/qtm
[15:15] -queuebot:#ubuntu-ci-eng- abeato, https://bileto.ubuntu.com/#/ticket/2472 Successfully built
[15:17] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2514 Successfully built (xenial/unity-api, zesty/unity-api). Uploading build (xenial/unity8, zesty/unity8)
[15:28] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Chroot problem (zesty/ubuntu-keyboard). Failed to build (zesty/indicator-keyboard). Needs rebuild due to new commits (zesty/unity8). Pending binary packages (xenial/ubuntu-system-settings, zesty/ubuntu-system-settings). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-touch-session, xenial/u
[15:32] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2515 Preparing packages
[15:36] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2514 Pending binary packages (xenial/unity8, zesty/unity8). Successfully built (xenial/unity-api, zesty/unity-api)
[15:47] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[15:56] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 zesty/ubuntu-system-settings: Failed to download DSC file https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/2481/+files/ubuntu-system-settings_0.4+17.04.20170224.3-0ubuntu1.dsc
[15:56] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2515 Ready to build
[15:56] -queuebot:#ubuntu-ci-eng- mzanetti, https://bileto.ubuntu.com/#/ticket/2514 Successfully built
[15:57] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2515 Preparing packages
[15:59] <jgdx> ahayzen, doesn't seem the diffs are uploaded
[15:59] <jgdx> wonder if the target is wrong
[15:59] <ahayzen> jgdx, hmm weird
[16:00] <ahayzen> jgdx, maybe the MP needs to propose into trunk ? rather than our middle branch ?
[16:00] <jgdx> ahayzen, maybe, if this one fails too
[16:01] <jgdx> ahayzen, then I guess you have to do it, as i'm one foot out the door
[16:01] <ahayzen> jgdx, i'll watch what happens this time :-)
[16:01] <jgdx> ahayzen, thank you
[16:03] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[16:04] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 zesty/ubuntu-system-settings: Failed to branch https://code.launchpad.net/~michael-sheldon/ubuntu-system-settings/show-osk-setting
[16:24] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[16:37] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2515 Failed to build
[16:44] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2515 Preparing packages
[16:48] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Chroot problem (zesty/ubuntu-keyboard). Currently building (xenial/ubuntu-system-settings, xenial/unity8, zesty/ubuntu-system-settings, zesty/unity8). Failed to build (zesty/indicator-keyboard). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-touch-session, zesty/qtmir, zesty/qtmir-gles, ze
[16:57] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2515 Failed to build (xenial/ubuntu-ui-extras). Needs rebuild due to new commits (zesty/ubuntu-ui-extras)
[16:57] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2515 Preparing packages
[17:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Chroot problem (zesty/ubuntu-keyboard). Currently building (xenial/ubuntu-system-settings, zesty/ubuntu-system-settings). Failed to build (zesty/indicator-keyboard). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-touch-session, xenial/unity8, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu,
[17:27] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Chroot problem (zesty/ubuntu-keyboard). Failed to build (zesty/indicator-keyboard). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, xenial/unity8, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, zesty/qtubuntu-gles, zesty/ubuntu-system-settings,
[17:27] -queuebot:#ubuntu-ci-eng- oSoMoN ahayzen, https://bileto.ubuntu.com/#/ticket/2510 Publishing packages
[17:53] -queuebot:#ubuntu-ci-eng- oSoMoN ahayzen, https://bileto.ubuntu.com/#/ticket/2510 Proposed pocket (zesty/ubuntu-ui-extras). Release pocket (xenial/ubuntu-ui-extras)
[17:57] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2515 Destination version missing from changelog (zesty/ubuntu-ui-extras). Successfully built (xenial/ubuntu-ui-extras)
[18:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Chroot problem (zesty/ubuntu-keyboard). Failed to build (zesty/indicator-keyboard). Needs rebuild due to new commits (zesty/unity8). Successfully built (xenial/indicator-keyboard, xenial/qtmir, xenial/qtmir-gles, xenial/qtubuntu, xenial/qtubuntu-gles, xenial/ubuntu-keyboard, xenial/ubuntu-system-settings, xenial/ubuntu-touch-session, xenial/unity8, zesty/qtmir, zesty/qtmir-gles, zesty/qtubuntu, ze
[18:19] -queuebot:#ubuntu-ci-eng- renatofilho tiagosh boiko, https://bileto.ubuntu.com/#/ticket/2318 Preparing packages
[18:45] -queuebot:#ubuntu-ci-eng- renatofilho tiagosh boiko, https://bileto.ubuntu.com/#/ticket/2318 Currently building (xenial/telephony-service). Dependency wait (zesty/telephony-service). Failed to build (zesty/history-service, zesty/telepathy-ofono). Successfully built (xenial/empathy, xenial/history-service, xenial/telepathy-mission-control-5, xenial/telepathy-ofono, zesty/empathy, zesty/telepathy-mission-control-5)
[19:05] -queuebot:#ubuntu-ci-eng- renatofilho tiagosh boiko, https://bileto.ubuntu.com/#/ticket/2318 Dependency wait (zesty/telephony-service). Failed to build (zesty/history-service, zesty/telepathy-ofono). Successfully built (xenial/empathy, xenial/history-service, xenial/telepathy-mission-control-5, xenial/telepathy-ofono, xenial/telephony-service, zesty/empathy, zesty/telepathy-mission-control-5)
[19:21] -queuebot:#ubuntu-ci-eng- boiko tiagosh renato, https://bileto.ubuntu.com/#/ticket/2451 Needs rebuild due to new commits (vivid/address-book-app, vivid/history-service, vivid/messaging-app, vivid/messaging-framework, vivid/telephony-service, vivid/ubuntu-system-settings). Successfully built (vivid/dialer-app, vivid/mfw-plugin-irc, vivid/telepathy-ofono)
[19:33] -queuebot:#ubuntu-ci-eng- oSoMoN ahayzen, https://bileto.ubuntu.com/#/ticket/2510 Release pocket
[19:35] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://bileto.ubuntu.com/#/ticket/2311 Preparing packages
[19:39] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Dependency wait (zesty/qtubuntu-print). Failed to build (xenial/ubuntu-printing-app, xenial/ubuntu-ui-extras, zesty/ubuntu-printing-app). Needs rebuild due to new commits (zesty/ubuntu-ui-extras). Successfully built (xenial/content-hub, xenial/qtubuntu-print, zesty/content-hub)
[19:59] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2483 Preparing packages
[20:02] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://bileto.ubuntu.com/#/ticket/2311 Failed to build (xenial/telepathy-qt, zesty/telepathy-qt). Pending binary packages (xenial/messaging-app). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/libircclient, xenial/messaging-framework, xenial/mfw-plugin-irc, zesty/address-book-app, zesty/address-book-service, zesty/libircclient, zesty/messaging-app, zesty/messaging-framework, zesty/mfw-pl
[20:22] -queuebot:#ubuntu-ci-eng- tiagosh bfiller boiko, https://bileto.ubuntu.com/#/ticket/2311 Failed to build (xenial/telepathy-qt, zesty/telepathy-qt). Successfully built (xenial/address-book-app, xenial/address-book-service, xenial/libircclient, xenial/messaging-app, xenial/messaging-framework, xenial/mfw-plugin-irc, zesty/address-book-app, zesty/address-book-service, zesty/libircclient, zesty/messaging-app, zesty/messaging-framework, zesty/mfw-plugin-irc)
[20:26] -queuebot:#ubuntu-ci-eng- dobey, https://bileto.ubuntu.com/#/ticket/2483 Successfully built
[20:40] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Preparing packages
[20:40] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 zesty/ubuntu-ui-extras: Failed to branch https://code.launchpad.net/~phablet-team/ubuntu-ui-extras/printer-components
[20:43] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2381 Failed to build (xenial/ubuntu-ui-extras). Needs rebuild due to new commits (zesty/ubuntu-ui-extras). Successfully built (xenial/ubuntu-settings-components, xenial/ubuntu-system-settings, zesty/ubuntu-settings-components, zesty/ubuntu-system-settings)
[20:43] -queuebot:#ubuntu-ci-eng- boiko tiagosh renato, https://bileto.ubuntu.com/#/ticket/2451 Needs rebuild due to new commits (vivid/address-book-app, vivid/dialer-app, vivid/history-service, vivid/messaging-app, vivid/messaging-framework, vivid/telephony-service, vivid/ubuntu-system-settings). Successfully built (vivid/mfw-plugin-irc, vivid/telepathy-ofono)
[20:45] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Preparing packages
[20:46] -queuebot:#ubuntu-ci-eng- boiko tiagosh, https://bileto.ubuntu.com/#/ticket/2283 Needs rebuild due to new commits (zesty/dialer-app, zesty/ubuntu-system-settings). Successfully built (xenial/dialer-app, xenial/tone-generator, xenial/ubuntu-system-settings, zesty/tone-generator)
[20:57] -queuebot:#ubuntu-ci-eng- jgdx ahayzen, https://bileto.ubuntu.com/#/ticket/2515 Needs rebuild due to new commits (zesty/ubuntu-ui-extras). Successfully built (xenial/ubuntu-ui-extras)
[20:59] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Dependency wait (zesty/qtubuntu-print). Failed to build (xenial/ubuntu-printing-app, zesty/ubuntu-printing-app). Pending binary packages (xenial/ubuntu-ui-extras, zesty/ubuntu-ui-extras). Successfully built (xenial/content-hub, xenial/qtubuntu-print, zesty/content-hub)
[21:05] -queuebot:#ubuntu-ci-eng- renatofilho tiagosh boiko, https://bileto.ubuntu.com/#/ticket/2318 Failed to build (zesty/history-service, zesty/telepathy-ofono). Needs rebuild due to new commits (zesty/telephony-service). Successfully built (xenial/empathy, xenial/history-service, xenial/telepathy-mission-control-5, xenial/telepathy-ofono, xenial/telephony-service, zesty/empathy, zesty/telepathy-mission-control-5)
[21:19] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Dependency wait (zesty/qtubuntu-print). Failed to build (xenial/ubuntu-printing-app, zesty/ubuntu-printing-app). Successfully built (xenial/content-hub, xenial/qtubuntu-print, xenial/ubuntu-ui-extras, zesty/content-hub, zesty/ubuntu-ui-extras)
[21:44] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Preparing packages
[21:51] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Preparing packages
[22:18] -queuebot:#ubuntu-ci-eng- kenvandine ahayzen, https://bileto.ubuntu.com/#/ticket/2236 Dependency wait (zesty/qtubuntu-print, zesty/ubuntu-printing-app). Successfully built (xenial/content-hub, xenial/qtubuntu-print, xenial/ubuntu-printing-app, xenial/ubuntu-ui-extras, zesty/content-hub, zesty/ubuntu-ui-extras)
[23:08] -queuebot:#ubuntu-ci-eng- ltinkl, https://bileto.ubuntu.com/#/ticket/2481 Successfully built


[03:15] <etank> class is in session :)
[03:15] <crimsun> ok, the first thing I did was rename wine-doors-0.1pre1.tar.gz to wine-doors_0.1~pre1.orig.tar.gz
[03:16] <crimsun> I then extracted it (tar xf)
[03:16] <etank> ok
[03:16] <crimsun> I then removed the existing debian symlink and recreated dist/debian as debian-upstream
[03:17] <crimsun> I then created a new debian subdir and cp'd everything in debian-upstream into debian
[03:17] <etank> you recreated the symlink as debian-upstream?
[03:17] <crimsun> yes, you also could have used mv
[03:18] <crimsun> completely your prerogative.  I intend to leave a pointer to the existing upstream structure as closely as possible.
[03:18] <crimsun> At this point you should decide what packaging scheme you wish to use.
[03:19] <crimsun> The existing debian-upstream approach is fairly straightforward debhelper.
[03:19] <etank> whatever is easy to use / learn and works
[03:19] <crimsun> Well, I can't make that call for you. :)
[03:19] <etank> in this case what would you recommend using?
[03:19] <crimsun> well, I'd use cdbs.
[03:20] <crimsun> As the maintainer, you have to weigh some choices.
[03:20] <crimsun> Using cdbs introduces an additional build-dependency but simplifies your debian/rules
[03:20] <etank> at this point i am still learning so cdbs is fine with me
[03:21] <crimsun> ok, make sure you have a Web browser window/tab open to https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml
[03:21] <etank> ok
[03:22] <etank> i was looking at that and the docs that were installed with cdbs on my system
[03:22] <crimsun> we can start with something straightforward.  Let's fix debian/changelog
[03:23] <crimsun> e.g., http://pastebin.ca/543266
[03:23] <crimsun> (I've not changed the date -R yet, but you can do that)
[03:24] <etank> would you use 'dch -i' for this ?
[03:24] <crimsun> I don't recommend it, since you only need one entry.
[03:24] <crimsun> I would just recreate debian/changelog
[03:25] <crimsun> You can accomplish that with your favorite $EDITOR
[03:27] <etank> recreate or just add to the top of the existing one?
[03:27] <crimsun> the former
[03:27] <crimsun> it doesn't make sense to retain the existing debian/changelog entries
[03:28] <etank> i would have thought that the creators changes would need to be included
[03:28] <etank> done
[03:29] <crimsun> no, they only need to be retained _inside the distro_
[03:29] <crimsun> since you're working on the initial packaging for the Ubuntu distro, your changelog entry is the first.
[03:29] <etank> i see
[03:30] <crimsun> Furthermore, the original changelog is preserved in debian-upstream/changelog if anyone truly wishes to inspect the pedigree
[03:30] <etank> makes sense
[03:33] <crimsun> after you've modified debian/changelog, it's time to make a note regarding the symlink change.
[03:33] <crimsun> cat >README.Debian-Source\
[03:33] <crimsun> err
[03:33] <crimsun> cat >README.Debian-Source
[03:33] <crimsun> The debian/ shipped in upstream has been recreated as a symlink
[03:33] <crimsun> (debian-upstream -> dist/debian).
[03:33] <crimsun> ^D
[03:34] <crimsun> (this is inside debian/, BTW)
[03:34] <etank> so i add that to the README ?
[03:34] <crimsun> using the precise syntax I've given you
[03:34] <crimsun> README.Debian-Source is the filename
[03:35] <etank> done
[03:36] <crimsun> ok, the next file to modify is debian/control
[03:36] <crimsun> you'll need to add cdbs as a build-dependency
[03:37] <etank> is that as @cdbs@ ?
[03:37] <crimsun> no, just cdbs.
[03:37] <crimsun> you'll also need to bump the minimum required version of debhelper to >= 5
[03:37] <etank> should the standards version be changed?
[03:38] <etank> or does that matter?
[03:38] <crimsun> I would bump it to 3.7.2; we'll ensure later that it adheres to Policy 3.7.2.
[03:39] <etank> maintainer stays as the upstream person right
[03:39] <crimsun> next up is to change the Maintainer field according to https://wiki.ubuntu.com/DebianMaintainerField
[03:40] <crimsun> after that, I'd change the Description
[03:41] <crimsun> e.g., http://pastebin.ca/543300
[03:42] <crimsun> then:
[03:42] <crimsun> cat >compat
[03:42] <crimsun> 5
[03:42] <crimsun> ^D
[03:42] <crimsun> (that's for debhelper compat)
[03:42] <etank> i need to add a XSBC-Original-Maintainer right?
[03:43] <crimsun> no, because there's no Debian maintainer yet
[03:43] <crimsun> thus, the only Maintainer is MOTU.
[03:44] <etank> changes made
[03:44] <crimsun> ok, so let's review.
[03:44] <crimsun> so far we've modified/created changelog, compat, control, and README.Debian-Source
[03:45] <etank> right
[03:45] <crimsun> ok, next up is debian/menu
[03:46] <crimsun> it needs to be reformatted: e.g., http://pastebin.ca/543308
[03:46] <etank> compat went in debian too right?
[03:46] <crimsun> correct.
[03:47] <etank> ok
[03:47] <etank> so all that was done in menu was moving each element to a seperate line?
[03:48] <etank> is that just to make it easier to read later
[03:48] <crimsun> formatting is important, and yes.
[03:48] <crimsun> those are tabs, BTW.
[03:48] <etank> my vim converts a tab to 4 spaces. will that work OK?
[03:49] <crimsun> I'd use a tab.
[03:50] <etank> done
[03:51] <crimsun> ok, next up is debian/copyright
[03:52] <crimsun> e.g., http://pastebin.ca/543315
[03:53] <crimsun> note that that debian/copyright is incomplete
[03:53] <crimsun> you need to further modify it so it mentions Debian's/Ubuntu's inclusion of common licenses on the user's filesystem.
[03:55] <crimsun> note the additions of lines 35-39 at http://pastebin.ca/543321
[03:56] <etank> ok
[03:58] <crimsun> ok, now off to debian/rules
[03:59] <etank> this is one of the files that i just do not understand
[03:59] <etank> up until now i have understood most everything that we have done
[03:59] <crimsun> debian/rules is really the "heart" of Debian/Ubuntu packaging
[04:00] <etank> and it would be the "one" (really more than that) thing that i dont get
[04:01] <etank> cdbs is supposed to make it easier thought right
[04:01] <crimsun> it does
[04:01] <etank> is it like calling templates of rules?
[04:01] <crimsun> now, make sure you've got a Web browser window/tab open to https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml#id2528674
[04:01] <crimsun> we'll be following the New Python policy.
[04:02] <crimsun> (sorry, phone call)
[04:02] <etank> no problem at all
[04:05] <crimsun> (ok, back)
[04:06] <crimsun> essentially there are two Python approaches, python-support and python-central
[04:06] <crimsun> the nice thing is that you don't have to know a thing about either; you just have to pick one
[04:06] <etank> cool
[04:07] <crimsun> so, pick one :)
[04:07] <etank> it was heads so python-support
[04:08] <crimsun> ok, so you'll need a DEB_PYTHON_SYSTEM = pysupport  line
[04:09] <etank> where does it go
[04:09] <crimsun> before you include include /usr/share/cdbs/1/class/python-distutils.mk
[04:09] <crimsun> without the redundant include, of course
[04:10] <crimsun> (the New Python policy section in the CDBS documentation, which you're hopefully following alongside, documents that)
[04:11] <etank> so should i be starting with a clean rules file?
[04:11] <etank> i was trying to figure out where these lines go in the current one
[04:11] <crimsun> I'd delete everything except for the "python setup.py install -S --prefix=/ --temp=$(CURDIR)/debian/wine-doors/" line in the existing install: target
[04:16] <etank> does this look right?
[04:16] <etank> http://pastebin.ca/543389
[04:16] <etank> except i have #!/usr/bin/make -f on the first line
[04:18] <etank> http://pastebin.ca/543395
[04:20] <crimsun> sec, Internet connection is not cooperating
[04:37] <crimsun> ok
[04:37] <crimsun> sorry about that
[04:37] <crimsun> now
[04:37] <etank> np
[04:37] <crimsun> it turns out that you don't even need the Python policy
[04:38] <crimsun> it's actually much simpler
[04:38] <etank> simpler == better
[04:39] <crimsun> upstream's setup.py, however, is crackful
[04:39] <crimsun> they really ought to use distutils
[04:41] <crimsun> cf. http://pastebin.ca/543449
[04:41] <crimsun> note that you need to make corresponding changes to debian/control
[04:42] <crimsun> cf. http://pastebin.ca/543454
[04:43] <crimsun> note that you can erase debian/{config,*.template*} as both are unused
[04:43] <etank> no deb-conf?
[04:43] <crimsun> correct, see above.
[04:44] <crimsun> now, the last step for debian/control will be to roll in the dependencies.
[04:44] <crimsun> you'll need to add these from http://www.wine-doors.org/wordpress/?page_id=3
[04:46] <etank> all of them?
[04:46] <crimsun> well, some of them imply others
[04:46] <etank> right. wine calls cabextract
[04:47] <crimsun> no, not in that sense
[04:47] <crimsun> meaning, e.g., adding python-glade2 as a Depends to Package: wine-doors implies a dependency on python, so you don't list python as a dependency.
[04:48] <crimsun> python-glade2 also covers libcairo2 and python2.4-cairo
[04:49] <etank> so would this be correct?
[04:49] <etank> Depends: wine, python, python-glade2, python-libxml2
[04:50] <crimsun> nope
[04:50] <crimsun> Depends: wine, python-gnome2-desktop, python-libxml2, python-glade2
[04:51] <crimsun> now, at the expense of doing _all_ the packaging for you :), I'm going to just point out some remaining issues.
[04:51] <crimsun> most importantly, the man page needs fixing
[04:52] <crimsun> also very important is the fact that you need to reroll the original tarball with the debian-upstream symlink in place but _without_ the debian dir
[04:52] <crimsun> after you do that, you'll need to modify the version and the original tarball's filename to reflect this
[04:53] <crimsun> I've posted the rerolled tarball as http://adhd.irule.net/~crimsun/wine-doors_0.1~pre1.repacked.orig.tar.gz
[04:53] <crimsun> and the version that should be used in debian/changelog is 0.1~pre1.repacked-0ubuntu1
[04:54] <etank> im still up on the man page part
[04:54] <etank> what would need to be fixed there?
[04:54] <crimsun> the sections and the headers
[04:55] <crimsun> there are lots of walkthroughs to help you with that, so I'm not going to cover that here
[04:56] <crimsun> finally, the Debianized source package needs a full copy of the GPL.  Upstream's LICENSE file is insufficient; a complete copy of the GPL needs to ship with it.
[04:56] <etank> i thought that if it was a common license then it could just be mentioned where it is on the system
[04:57] <crimsun> no
[04:57] <crimsun> the license explicitly states that the user should have received a full copy of the GPL with the source code.
[04:57] <crimsun> "You should have received a copy of the GNU General Public License along with this program"
[04:57] <crimsun> if you do not ship a full copy of the GPL, the archive admins will reject the source package.
[04:59] <etank> i was going from http://www.debian.org/doc/maint-guide/ch-dreq.en.html#s-copyright  "License can be found in the file `/usr/share/common-licenses/GPL-2'."
[04:59] <crimsun> that should be in debian/copyright, yes.
[05:00] <crimsun> however, it is still required that the source package ship with a full copy of the GPL as per the terms of the license itself.
[05:01] <crimsun> do you have any additional questions thus far?
[05:01] <etank> i am so lost at this point i dont even know where to begin
[05:01] <crimsun> ok, where are you lost?
[05:02] <crimsun> have you understood the changes to [rerolled]  debian/ *
[05:02] <crimsun> debian/* , rather
[05:02] <crimsun> 1) changed changelog -> only 1 entry necessary
[05:02] <crimsun> 2) created compat (contents "5")
[05:03] <crimsun> 3) created README.Debian-Source (mentioned new symlink)
[05:03] <crimsun> 4) changed control
[05:03] <crimsun> 5) changed menu
[05:03] <crimsun> 6) changed rules
[05:03] <crimsun> 7) removed unnecessary files (*.template*, config)
[05:04] <crimsun> which of those seven changes is unclear at this point?
[05:04] <etank> i dont know what 2 was for
[05:04] <etank> i still dont get rules
[05:05] <crimsun> ok.  (2) is used because you have a versioned build-dependency in debian/control on debhelper (>= 5)
[05:05] <etank> why would a the symlink stuff go in README.Debian-Source and not in the changelog
[05:05] <etank> and i dont even remember what was changed in control
[05:06] <crimsun> you've simplified debian/rules (6) to use cdbs [along with debhelper, but cdbs will handle that for you because you've included the debhelper file]  and not just debhelper
[05:07] <crimsun> the symlink is mentioned in README.Debian-Source because you have to reroll (and thus rename) the original upstream tarball
[05:07] <etank> what is the process of doing that
[05:07] <crimsun> to what does "that" refer?
[05:07] <etank> i can create a tarball but what needs to be changed in the rerolling?
[05:08] <crimsun> ok, here, I'll walk you through that part
[05:08] <crimsun> create a scratch dir and CWD into it
[05:08] <crimsun> then, extract the _original_ upstream tarball
[05:09] <crimsun> then CWD into the root of the extracted source
[05:09] <etank> <dumb question> by CWD into it you mean just 'cd scatch'
[05:09] <crimsun> yes
[05:09] <crimsun> CWD == change working directory
[05:09] <crimsun> now note how the extracted original upstream tarball has debian -> dist/debian//
[05:10] <etank> yup
[05:10] <crimsun> we want that to actually be debian-upstream -> dist/debian/
[05:11] <crimsun> so, we'll do this:  mv debian debian-upstream
[05:11] <etank> ok
[05:11] <crimsun> next, we need to reroll this current version as the "repacked" tarball.
[05:12] <etank> so that was it
[05:12] <crimsun> so, we'll back out one directory (cd ..) and use tar+gzip to reroll the "original" [which is now the "repacked"]  tarball
[05:12] <etank> moving the symlink to match what was done
[05:13] <etank> tar zcvf wine-doors_0.1~pre1.repacked.orig.tar.gz wine-doors-0.1pre1 ?
[05:13] <crimsun> tar cf wine-doors_0.1~pre1.orig.repacked.tar wine-doors-0.1pre1/
[05:13] <crimsun> && gzip -9 wine-doors_0.1~pre1.orig.repacked.tar
[05:13] <crimsun> sorry
[05:13] <crimsun> wrong order
[05:14] <crimsun> tar cf wine-doors_0.1~pre1.repacked.orig.tar wine-doors-0.1pre1/
[05:14] <crimsun> gzip -9 wine-doors_0.1~pre1.repacked.orig.tar
[05:15] <crimsun> then when you extract it, you'll create debian/ in that repacked version and go through those 7 changes listed above
[05:15] <crimsun> this is good practice, since you should reroll that tarball with the full version of the GPL included as COPYING
[05:16] <crimsun> is that a bit clearer?
[05:16] <etank> somewhat
[05:16] <crimsun> ok.
[05:16] <etank> would the tar command that i typed have done the same thing?
[05:16] <crimsun> sure
[05:16] <etank> just checking
[05:17] <etank> one last question
[05:17] <crimsun> (although I always use tar & gzip -9 as separate steps due to some systems locally using a different compression level by default)
[05:18] <etank> once all of the stuff is done what command is used to create the deb
[05:18] <crimsun> debuild -S -sa -uc -us
[05:18] <etank> i used debuild -S before and then sudo pbuilder ../*.dsc
[05:18] <crimsun> or, if you have a GPG key already posted, debuild -S -sa -k0xfoo
[05:19] <crimsun> and then, yes, pass the dsc to pbuilder build
[05:20] <etank> ok
[05:21] <etank> i still have lots of questions but i will have to ask them later
[05:21] <crimsun> these steps will get you started with a wine-doors source package
[05:21] <etank> i dont think my brain can handle much more
[05:21] <crimsun> that's ok, I covered a lot more than just converting to CDBS
[05:21] <etank> thank you for all your help
[05:21] <crimsun> np, anytime.
[05:22] <etank> the only place that i even saw cdbs come into play was in control and rules
[05:22] <crimsun> correct
[05:22] <etank> but i guess that it gets called by debuild
[05:22] <crimsun> well, what ultimately builds the package is dpkg-buildpackage(1)
[05:22] <etank> i think that i am starting to understand the mechanics of it all
[05:23] <etank> just not how the files need to be laid out for it all to work
[05:23] <etank> that and the policies
[05:23] <crimsun> CDBS is just a system of redefined Makefile rules to make your life a bit easier
[05:23] <etank> like sending the full GPL with it
[05:23] <crimsun> yes, there are lots of policies - too many to cover in just a few hours
[05:24] <crimsun> it'll take a good few months to become exposed to the myriad policies at work
[05:24] <etank> other than playing like this, what else can i do to learn more about MOTU(ing)
[05:24] <crimsun> a good place to supplement packaging is the Debian New Maintainer's Guide
[05:24] <etank> i've read that
[05:25] <etank> then i read the ubuntu packagingguide
[05:25] <crimsun> the Contributing wiki page linked in the topic of #ubuntu-motu is helpful (hopefully)
[05:27] <etank> i will look at that again tomorrow
[05:27] <etank> thanks again for the help
[05:27] <etank> good night